Critical VMware vCenter Authentication Bypass (CVE-2026-123890, CVSS 9.8): Broadcom VMSA-2026-0009 Says Patch Now, No Workaround

An unauthenticated network flaw in vCenter's VMware Directory Service lets attackers bypass authentication; fixed in 9.1.1.0200, 9.0.2.0200, 8.0 U3m and VCF 5.2.5, with no workaround.
Overview
Broadcom has released VMware Security Advisory VMSA-2026-0009, rated Critical, fixing a pre-authentication flaw in VMware vCenter tracked as CVE-2026-123890 (CVSSv3 9.8). The bug is in the VMware Directory Service (vmdir), which handles identity in vCenter. An attacker who can reach vCenter over the network can bypass authentication and gain unauthorized access to the system. Broadcom lists no workaround: patching is the only fix.
The advisory came out on 19 November 2026, and the CVE record was published at 18:02 Mauritius time (14:02 UTC). Broadcom's own Q&A says the vCenter issue qualifies as an emergency change under ITIL.
The Vulnerability
- CVE: CVE-2026-123890, vCenter authentication-bypass vulnerability
- Weakness: CWE-288, Authentication Bypass Using an Alternate Path or Channel
- Component: VMware Directory Service in vCenter
- CVSSv3.1: 9.8 Critical, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Attack requirements: network access to vCenter only; no credentials and no user interaction
- Workaround: none
Fixed versions from the Broadcom response matrix:
- vCenter 9.1.x (VMware Cloud Foundation / vSphere Foundation 9.1): fixed in 9.1.1.0200
- vCenter 9.0.x (VCF / VVF 9.0): fixed in 9.0.2.0200
- vCenter 8.0: fixed in 8.0 U3m
- vCenter 7.0: affected; customers with an extended support contract must contact Broadcom Support for a fix
- VMware Cloud Foundation 5.x: fixed in 5.2.5, using the async patching guide (KB88287)
- Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 and Telco Cloud Infrastructure 3.0: see KB463116
Broadcom notes that patches are cumulative, so any later build also contains the fix.
Other Flaws in the Same Advisory
VMSA-2026-0009 fixes four more issues. Their scores range from 6.7 to 8.1:
- CVE-2026-123891 (8.1, Important): SQL injection in SDDC Manager. An authenticated attacker can read and write the database.
- CVE-2026-123892 (7.2, Important): authenticated command injection in SDDC Manager, leading to arbitrary commands on the appliance
- CVE-2026-123893 (6.7, Moderate): local privilege escalation in SDDC Manager, from admin to root
- CVE-2026-123894 (6.7, Moderate): SAML token signature bypass in VMware Tools for Windows. On guests configured with Guest Alias mapping, it allows privilege escalation inside the VM.
For VCF, version 9.1.1.0200 contains the fixes for all of the SDDC Manager CVEs.
Timeline
- 6 November 2026: CVE ID reserved by VMware as CNA
- 19 November 2026, 18:02 Mauritius time (14:02 UTC): VMSA-2026-0009 and the CVE record published
- 19 November 2026, 19:17 Mauritius time (15:17 UTC): record received by NVD
- 19 November 2026: CISA's SSVC enrichment rates the flaw Exploitation: none, Automatable: yes, Technical Impact: total
Tradecraft
The flaw was privately reported to Broadcom. There are no public reports of exploitation, and no public proof-of-concept is known at the time of writing, and the CVE is not in CISA's KEV catalog. History is the concern. vCenter bugs are a favourite target of ransomware crews and state-backed groups because vCenter controls every ESXi/ESX host and VM it manages. Earlier critical vCenter flaws were weaponised within days of disclosure. A no-credentials, network-reachable bypass that CISA rates as automatable fits that pattern.
Once an attacker has control of vCenter, they can typically:
- create or take over admin accounts and SSO identities
- snapshot, clone or export VMs, including domain controllers, to steal credentials offline
- push changes to hosts, enable SSH, and stage hypervisor-level ransomware or wipers
IOCs
Broadcom has not published any indicators of compromise, and no exploitation has been observed so far. Reef will update this item if that changes.
Detection
- Inventory every vCenter instance and its build number, including ones embedded in VCF, vSphere Foundation and Telco Cloud stacks. Flag anything below the fixed versions above.
- Check whether any vCenter interface is exposed to the internet or to untrusted networks. vCenter management should only be reachable from a dedicated admin network.
- Review vCenter SSO and directory service logs for logins or token issuance that don't match a normal authentication flow. Also look for new local or SSO accounts, role and permission changes, and new identity sources.
- Watch for unexpected VM snapshots, clones or OVF exports, SSH being enabled on hosts, and new scheduled tasks on the appliance.
Recommended Actions
- Patch now: treat this as an emergency change. Move to 9.1.1.0200, 9.0.2.0200, 8.0 U3m or VCF 5.2.5 as applicable. Telco Cloud users should follow KB463116.
- vCenter 7.0 is affected. If you have extended support, contact Broadcom; otherwise plan an upgrade to a supported line.
- Until you have patched, restrict network access to vCenter (firewall or ACL to admin jump hosts only). This reduces exposure but is not an official workaround.
- Patch SDDC Manager and VMware Tools for Windows from the same advisory in the same maintenance window.
- Rotate vCenter administrator and SSO credentials after patching if vCenter was reachable from untrusted networks.
- Subscribe to Broadcom's VMSA mailing list and follow the official Q&A for updates.
Analyst Assessment
Severity: Critical. It is an unauthenticated network flaw in the identity layer of the system that controls the whole virtual estate, with no workaround. Exploitation is not confirmed today. Even so, the likelihood of a public exploit and mass scanning soon is high, given how attractive vCenter is to attackers and how fast earlier vCenter bugs were weaponised. Organisations in Mauritius and the region that run vSphere for core banking, government or hosting should patch within days, not wait for the next monthly cycle.
