vCenter CVE-2026-123890 Auth Bypass Exploited as 0-Day
vCenter CVE-2026-123890 is an exploited CVSS 9.8 authentication bypass. CISA set a November 23 deadline. Patch vCenter and hunt rogue SSO admins.
CISA added vCenter CVE-2026-123890 to the Known Exploited Vulnerabilities catalog on November 20, 2026, one day after Broadcom patched it, with a federal due date of November 23. The flaw is a CVSS 9.8 authentication bypass in the VMware Directory Service that gives an unauthenticated attacker with network access an administrator session on vCenter Server. Google's Mandiant says the China-linked group ARMORY CASTLE used it as a zero-day from early September. Patch every vCenter now, then check for rogue SSO accounts.
What happened
Broadcom published VMSA-2026-0009 on November 19, 2026. It covers five CVEs across vCenter, SDDC Manager and VMware Tools for Windows. The one that matters most is CVE-2026-123890, which Broadcom describes as an authentication bypass in the VMware Directory Service (vmdir). Broadcom rates it Critical with a CVSSv3 base score of 9.8 and credits Mandiant for the report. There is no workaround.
The same day, Mandiant and Google Threat Intelligence Group (GTIG) published a report on ARMORY CASTLE, the suspected PRC-nexus espionage group formerly tracked as UNC5221. Forensic evidence shows the group exploited CVE-2026-123890 in early September 2026, more than two months before the patch. Broadcom's own advisory does not mention in-the-wild exploitation, a gap that both BleepingComputer and SecurityWeek noted.
CISA settled the question on November 20 by adding the CVE to KEV with a three-day remediation window under BOD 26-04 and a forensic triage flag set to Yes. That flag means federal agencies must look for compromise, not just install the update. GTIG analyst Kelli Vanderlee told Cybersecurity Dive that a small number of organizations are confirmed compromised so far, with more likely.
Who is affected
Every supported vCenter line needs the update. The fixed versions in the advisory are:
- vCenter 9.1.x: 9.1.1.0200
- vCenter 9.0.x: 9.0.2.0200
- vCenter 8.0: 8.0 U3m
- VMware Cloud Foundation 5.x: vCenter 8.0 U3m through the asynchronous patching process in KB 88287, plus SDDC Manager 5.2.5
- vCenter 7.0: no public patch. vSphere 7 reached end of general support on October 2, 2025, and Broadcom updated the advisory on November 20 to say customers with an extended support contract should request the fix through support.
- Telco Cloud Platform and Telco Cloud Infrastructure: see Broadcom KB463116
Broadcom's FAQ adds that vSphere 6.5 and 6.7 should be presumed vulnerable, that Enhanced Linked Mode makes no difference, and that ESX hosts, NSX, VCF Operations and VCF Automation are not affected by this advisory. Mandiant reports that the BONESAW exploit tool works against vCenter 7.x and 8.x appliances.
Broadcom's FAQ also states this is a new and distinct issue from CVE-2026-59309, the vmdir LDAP authentication bypass disclosed in July. Mandiant observed BONESAW succeed against a vCenter that was already patched for CVE-2026-59309. If you patched in August and stopped there, you are exposed. We covered the July advisory and its ransomware follow-on in our report on CVE-2026-59310 and the Babuk ESXi campaign.
How the vCenter bug works
Mandiant describes CVE-2026-123890 as an unauthenticated Secure Remote Password (SRP-6a) session key disclosure over DCE/RPC. The vulnerable service listens on TCP port 2012, the control interface for vCenter Single Sign-On. A flaw in how the SRP verifier service handled session keys let an attacker obtain the shared session key without knowing any password, which the exploit turned into an authenticated session as administrator@vsphere.local. For background on why a leaked session key defeats a password protocol, see what Secure Remote Password is and how it is supposed to work.
With that session, ARMORY CASTLE's Go tool BONESAW did four things, according to Mandiant:
- Streamed a copy of the vmdir database file data.mdb, an LMDB store, for offline parsing.
- Extracted the private RSA signing key of the Security Token Service (STS), the component that signs vCenter's SAML tokens.
- Created a backdoor machine account in vmdir and a new SSO administrator account.
- Assigned Global Administrator privileges on the vCenter root folder through the vSphere API.
A second tool, SAWSNAKE, used the stolen signing key to forge SAML assertions for the Administrator account and obtain session cookies. That is a Golden SAML attack: it bypasses MFA and impersonates any user for as long as the signing key stays valid. The actor then enabled SSH on the appliance through the VAMI management API, copied the vCenter master crypto key and the PostgreSQL password file, disabled SSH again, and pivoted to an ESXi host. On ESXi, Mandiant saw the group mount VMFS volumes and extract the Active Directory database (NTDS), the SYSTEM and SECURITY registry hives and DNS data straight out of a domain controller's virtual disk.
The intrusion did not start at vCenter. Initial access came through CVE-2026-102764, the BeyondTrust Remote Support zero-day that CISA added to KEV on October 16 and that we covered in our BeyondTrust report. From the Remote Support appliance, the group moved to internal Linux appliances without EDR, dropped web shells, escalated to root and scanned for VMware-specific ports: 9080, 5480 and 2012. Mandiant also found that the BONESAW binary carries a Go build timestamp of July 13, 2026, sixteen days before CVE-2026-59309 was disclosed. Go build metadata can be altered, but the timing suggests the actor held this bug before the July advisory existed.
What to do now
- Patch today. Apply 9.1.1.0200, 9.0.2.0200 or 8.0 U3m. The FAQ confirms the patch is available through the VAMI, that running workloads keep running during a vCenter update, and that these builds are not eligible for vCenter Quick Patch. One known issue: 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1, and Broadcom says to wait briefly for VCF 9.1.2 if you are mid-upgrade.
- Confirm the build. Broadcom's FAQ says the build number is on the Summary tab of the vSphere Client, or in PowerCLI after Connect-VIServer through the variable
$global:DefaultVIServer.Build. - Treat exposure since September as a possible compromise. Mandiant CTO Charles Carmakal said organizations should both apply the patches and examine their systems for evidence of compromise. Work through how to audit vCenter SSO accounts after a compromise: list every vsphere.local account and Administrators group member, look for names you did not create (Mandiant saw an account named with an sps prefix), review the STS signing certificate, and check whether SSH was toggled on the appliance.
- Rotate what the attacker could have taken. If you find signs of access, the STS signing key, the vCenter master key, the PostgreSQL credentials and every ESXi root credential are all suspect. Broadcom's KB 318968 points to the vCert tool for replacing the STS signing certificate.
- Hunt downstream. Check ESXi hosts for unexpected SSH authorized keys on the root account, hidden directories on VMFS datastores, and vpxuser logins at unusual times. Watch for the SSH banner
SSH-2.0-pulsesecure_23345, which Mandiant tied to the BEARBONES backdoor and a network of compromised routers and firewalls. Mandiant's report lists eleven suspected infrastructure IPs and six file names. - Reduce the blast radius for the next one. Mandiant's report is blunt about why the default appliance firewall did not stop this chain. Read why the vCenter appliance firewall is not enough before the next zero-day.
What to watch next
Broadcom's advisory is at revision .1 and may be updated again, especially if 7.0 extended-support patches ship more widely. Watch the KEV entry for a change in the ransomware field, which is currently Unknown. ARMORY CASTLE has now burned two zero-days in one campaign, and Mandiant says BONESAW was likely built for broader operations, so expect other victims to surface. Mandiant also noted that port 2012 is reachable from any host that can reach vCenter at all. If your backup server, monitoring host or jump box can talk to vCenter on every port, that is the path this group took.
Sources
- Broadcom: VMSA-2026-0009 vCenter, Tools and SDDC Manager security advisory
- Broadcom: VMSA-2026-0009 questions and answers
- Google Threat Intelligence Group and Mandiant: ARMORY CASTLE exploits vSphere
- CISA: Known Exploited Vulnerabilities catalog entry for CVE-2026-123890
- CVE.org: CVE-2026-123890 record
- BleepingComputer: VMware patches vCenter zero-day exploited in attacks since September
- SecurityWeek: Newly patched VMware vCenter flaw exploited as zero-day by Chinese APT
- Cybersecurity Dive: Chinese espionage group targets critical flaw in VMware vCenter
- Broadcom KB 318968: Checking and replacing the STS signing certificate