CVE-2026-123890
November 19, 2026
·
0
Minutes Read

VMWare vCenter Critical Authentication Bypass

Advisory
Security Advisory
November 19, 2026
·
0
Minutes Read

VMWare vCenter Critical Authentication Bypass

Advisory
Security Advisory
November 19, 2026
·
0
Minutes Read
Kudelski Security Team
Find out more
table of contents
Share on
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Summary

Broadcom published VMSA-2026-0009 on 19 November 2026. It fixes a critical, unauthenticated authentication bypass in VMware vCenter plus four lower-severity issues in SDDC Manager and VMware Tools.

  • CVE-2026-123890 is an authentication bypass in the VMware Directory Service component of vCenter. CVSS 3.1 score 9.8 Critical.
  • Broadcom's stated attack vector: "A malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system."
  • Broadcom says the vCenter issue "qualifies under ITIL methodologies as an emergency change" and urges organizations to act promptly.
  • No workaround. The FAQ answers "Not as listed by Broadcom" to the question of workarounds, while noting that an organization's own perimeter and appliance firewall controls may provide compensating protection.
  • Exploitation status: Broadcom is not aware of in-the-wild exploitation or PoC code, and it does not state what level of access an attacker gains after the bypass.
  • This is the second critical VMware Directory Service authentication bypass of 2026. The earlier one, CVE-2026-59309, was patched on 29 July 2026 under VMSA-2026-0006 and was also rated 9.8; a separate directory traversal flaw, CVE-2026-59310, shipped in that same advisory.

Affected Systems and/or Applications

CVE-2026-123890 (vCenter), per the advisory response matrix:

  • vCenter 9.1.x, fixed in 9.1.1.0200
  • vCenter 9.0.x, fixed in 9.0.2.0200
  • vCenter 8.0, fixed in 8.0 U3m
  • vCenter 7.0: affected, but no public fix; request a patch through Broadcom Support under an active extended support contract. vSphere 7 reached End of General Support on 2 October 2025.
  • VMware Cloud Foundation 5.x (vCenter), fixed in 5.2.5, applied through the asynchronous patching process in KB88287
  • VMware Telco Cloud Platform (3.0, 4.x, 5.0.x, 5.1.x, 5.2) and Telco Cloud Infrastructure 3.0, fixed via KB463116
  • vSphere 6.5 and 6.7: presume affected; Broadcom no longer evaluates products past End of General Support

The same advisory fixes four lower-severity issues, rated 6.7 to 8.1, all of which require an authenticated or already privileged actor:

  • CVE-2026-123891 (8.1): SQL injection in SDDC Manager, fixed in 9.1.1.0200, 9.0.2.0100, or 5.2.5
  • CVE-2026-123892 (7.2): command injection in SDDC Manager, same fixed versions
  • CVE-2026-123893 (6.7): local privilege escalation to root on the SDDC Manager appliance, same fixed versions
  • CVE-2026-123894 (6.7): SAML token signature bypass in VMware Tools for Windows, exploitable only where Guest Alias mapping is configured and contained within the guest VM, fixed in VMware Tools 13.1.5.0 for 13.x and 12.5.5 for 12.3.x

Technical Details

The flaw is classified as CWE-288, Authentication Bypass Using an Alternate Path or Channel: an attacker reaches an authenticated path that skips the expected credential checks rather than defeating cryptographic control or guessing a password.

Broadcom has not disclosed the affected endpoint, the request shape, the root cause, or the privileges obtained after bypass, and there is no public proof of concept or technical analysis. Defensive value therefore comes from closing the hole and removing reachability, not from exploit signatures.

This is the second critical flaw in the same service this year; that matters for risk posture. Attacks on the July directory traversal flaw, CVE-2026-59310, began five days after disclosure, which German incident response firm QUIRSO assessed in August as moderately likely to be linked to a suspected China-nexus actor, compromising an estimated 361 IP addresses in 47 countries and deploying Babuk-derived ransomware on ESXi hosts. Broadcom has reported no attacks against the new bypass.

Mitigation

  1. Patch on an emergency timeline. Apply the fixed build for your branch using the standard vSphere or VCF update mechanisms. These updates are not eligible for vCenter Quick Patch.
  2. Restrict reachability until patched. Limit vCenter access to approved administrative networks and management jump hosts. Broadcom states that organizations must decide for themselves whether perimeter and appliance firewall protections are adequate, so this is a compensating control, not a substitute for patching.
  3. Hunt for prior compromise. Review vCenter and platform logs for new or unexpected accounts, changes to roles, permissions, or groups, authentication from unfamiliar sources, and unexpected datastore, network, or host configuration changes. Rotate administrative credentials and tokens after patching.
  4. Check for upgrade conflicts. Installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VCF 9.1.1, a "Back-in-Time" restriction.
  5. Patch SDDC Manager and VMware Tools for Windows in the same window, since the issues are addressed in the same maintenance cycle.

What the CFC is Doing

The CFC is monitoring the situation and analyzing the case to identify potential threat-hunting campaigns. This advisory will be updated if required.

References

‍

Related Post