VMware vCenter zero-day CVE-2026-123890 exploited since September
Google and Mandiant tie CVE-2026-123890, a critical vCenter auth-bypass zero-day (CVSS 9.8), to China-nexus Armory Castle. Exploited since September; Broadcom patched it November 19.
Broadcom patched a critical VMware vCenter zero-day on November 19 that a suspected China-nexus group had been exploiting since early September. CVE-2026-123890 is an unauthenticated authentication-bypass flaw in the VMware Directory Service (vmdird), scored 9.8. It is fixed in VMSA-2026-0009. If you run vCenter, patch today — there is no workaround.
What the bug does
Google Threat Intelligence Group (GTIG) and Mandiant describe it as a Secure Remote Password (SRP-6a) session-key disclosure over DCE/RPC. An unauthenticated attacker with network reach to vmdird recovers the session key and completes a login as administrator@vsphere.local — full control of the vSphere SSO domain. From there, the actors used a custom tool Mandiant tracks as BONESAW to copy the vCenter directory database (data.mdb) through the vmdirdbcp RPC interface and mint a new SSO administrator account. A second tool, SAWSNAKE, enables Golden SAML attacks against federated applications.
In the intrusions Mandiant investigated, the initial entry point was a separate BeyondTrust Remote Support zero-day, CVE-2026-102764 (CVSS 9.3).
Affected and fixed versions
Per Broadcom's advisory:
- VCF / vSphere Foundation 9.1.x → fixed in 9.1.1.0200
- VCF / vSphere Foundation 9.0.x → fixed in 9.0.2.0200
- vCenter 8.0 → fixed in 8.0 U3m
- VMware Cloud Foundation 5.2.x → fixed in 5.2.5
- vCenter 7.0 → no public fix listed; Broadcom directs extended-support customers to open a case
Telco Cloud Platform and Telco Cloud Infrastructure inherit the fix via vCenter 8.0 U3m.
Exploitation status
GTIG and Mandiant report in-the-wild exploitation as a zero-day beginning in early September — more than two months before the patch. Mandiant attributes the activity to a suspected China-nexus espionage group it calls Armory Castle (formerly UNC5221); the China nexus is assessed, not confirmed by indictment. A BONESAW build timestamp of July 13, 2026 suggests the group may have known of the flaw before the July 29 disclosure of the related CVE-2026-59309, though build metadata can be forged, so treat that timeline as indicative only.
Action checklist
- Apply VMSA-2026-0009 to every vCenter, VCF and vSphere Foundation instance — today. There is no mitigation short of the patch.
- If you are on vCenter 7.0, open a Broadcom support case; do not leave vmdird reachable while you wait.
- Assume the vCenter SSO signing key is compromised on any exposed instance. Rotate it and audit for unexpected
administrator@vsphere.localsessions and new SSO admin accounts. - Hunt for
vmdirdbcpRPC activity and unexpected reads ofdata.mdb. - Patch BeyondTrust Remote Support (CVE-2026-102764) if you run it — that was the initial access vector in observed cases.
Context
This is the second VMware zero-day tied to this cluster of activity in 2026. In late October, CrowdStrike linked the same China-nexus actor — which it tracks as Warp Panda — to CVE-2026-41709, an ESX logging flaw CISA added to KEV. The through-line is a group that pairs edge zero-days (BeyondTrust) with directory-service abuse to seize the virtualization control plane and forge SAML tokens. vCenter remains a top-value target precisely because one admin session is the whole estate.