vCenter is the control plane for VMware environments. It manages ESXi hosts, holds the SSO identity domain and can reach every VM. Admin on vCenter usually means admin on everything it manages. That’s why CVE-2026-123890 is a drop-everything patch.
What Broadcom fixed
Broadcom published VMSA-2026-0009 on November 19, 2026. It covers five CVEs (CVE-2026-123890 to CVE-2026-123894) across vCenter, SDDC Manager and VMware Tools for Windows, with scores from 6.7 to 9.8. The critical one:
- CVE-2026-123890, an authentication bypass in the VMware Directory Service in vCenter, rated 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
- An attacker only needs network access to vCenter. No credentials and no user interaction are required.
- Workarounds: none. Broadcom calls the vCenter update an emergency change. BleepingComputer notes it applies whether or not Enhanced Linked Mode is enabled.
- Rapid7 says this is a different bug from CVE-2026-59309, an earlier 2026 vCenter auth bypass. Systems patched for that one still need this update.
| Product | Affected | Fixed |
|---|---|---|
| VCF / vSphere Foundation vCenter | 9.1.x | 9.1.1.0200 |
| VCF / vSphere Foundation vCenter | 9.0.x | 9.0.2.0200 |
| VMware vCenter | 8.0 | 8.0 U3m |
| VMware vCenter | 7.0 | Contact Broadcom (extended support contracts only) |
| VMware Cloud Foundation | 5.x | 5.2.5 |
| Telco Cloud Platform / Infrastructure | 3.0, 4.x, 5.0.x, 5.1.x, 5.2 / 3.0 | See KB463116 |
How ARMORY CASTLE used it
Broadcom credits Mandiant with the report. Mandiant and Google Threat Intelligence Group say the suspected PRC-nexus group ARMORY CASTLE (formerly UNC5221) exploited the bug in early September 2026, more than two months before the patch. According to Mandiant’s write-up:
- Initial access was through a different zero-day, CVE-2026-102764 in BeyondTrust Remote Support, which Mandiant covered in October.
- The group moved to internal Linux appliances without EDR, dropped the SLIMSAVAGE and CAGEMATCH web shells, got root through an SUID trick using
gdb, and scanned for VMware ports 9080, 5480 and 2012. Port 2012 is the vCenter SSO control-interface RPC that the exploit uses. - Mandiant describes the bug as an unauthenticated SRP-6a session-key disclosure over DCE/RPC. It produces an authenticated session as
administrator@vsphere.local. - A custom Go tool, BONESAW, used that session to create an SSO administrator account, exfiltrate the directory’s LMDB database (
data.mdb) and hijack the SAML Security Token Service. - SAWSNAKE then ran Golden SAML attacks, forging tokens to bypass MFA and impersonate users. BleepingComputer, citing Mandiant, says the attackers eventually reached ESXi hosts and pulled data from VMs, including Active Directory database files.
The BEARBONES and LAZYBONES backdoors were also deployed. Two zero-days in one intrusion, plus malware built for each platform, point to a well-resourced actor that knows VMware internals.
What to do
- Patch vCenter now, outside your normal cycle. Rapid7 notes the fix can’t be applied with vCenter Quick Patch. Use the standard update path. During the update the management interfaces go down, but running VMs keep running.
- Check your upgrade path. Rapid7 notes that 8.0 U3m and 9.0.2.0200 add a “Back-in-Time” restriction that blocks upgrading to VCF 9.1.1. Read Broadcom’s FAQ if you’re mid-upgrade.
- On vCenter 7.0 without extended support, there’s no fix. Restrict network access to vCenter (including port 2012) to admin jump hosts and plan the upgrade.
- Assume SAML keys may be burned if vCenter was reachable from a compromised segment. Look for unknown SSO admin accounts, rotate the STS signing certificate, and review SSO logins that skipped MFA.
- Look at the doors in. ARMORY CASTLE came through a remote-support appliance and Linux boxes without EDR. Patch BeyondTrust Remote Support for CVE-2026-102764 and put EDR or at least integrity monitoring on appliances that can reach vCenter.