If you run VMware vCenter, stop reading after this paragraph and go schedule the patch. Then come back, because patching is only half of it.
Broadcom published VMSA-2026-0009 on November 19 for CVE-2026-123890, an authentication bypass in the vCenter Directory Service rated CVSS 9.8. The same day, Mandiant and Google Threat Intelligence Group said a suspected China-nexus espionage group they call ARMORY CASTLE (formerly tracked as UNC5221) has been exploiting it as a zero-day since early September. That's more than two months of quiet access before a fix existed.
What the Bug Does
Per Rapid7 and the write-ups of Mandiant's findings:
- No credentials needed. Anyone who can reach the vCenter Directory Service over the network can end up with an
administrator@vsphere.localsession. No password, no MFA prompt. - It's a new bug. This is not CVE-2026-59309, the vmdir auth bypass from July. Mandiant says the exploit worked against servers already patched for that one. If you remember patching vCenter this summer and feeling good about it, that feeling has expired.
- No workaround. Broadcom lists none, and the update can't go through vCenter Quick Patch. Running VMs keep running during the vCenter update; management goes away for a bit.
Fixed versions: vCenter 8.0 U3m, 9.0.2.0200, 9.1.1.0200, and VCF 5.2.5. vCenter 7.0 has no listed fix; extended-support customers are told to contact Broadcom. Heads up: per Rapid7, the 8.0 U3m and 9.0.2.0200 builds block a later upgrade to VCF 9.1.1, so check your upgrade path before you pick a build.
The same advisory fixes four lower-severity bugs in SDDC Manager and VMware Tools for Windows. Broadcom reports no exploitation of those.
What the Attackers Did With It
This is the part that should change your incident response plan. As described from Mandiant's report:
- The way in wasn't vCenter. The chain started on a BeyondTrust Remote Support zero-day (CVE-2026-102764, added to CISA's KEV catalog in October), moved to an internal Linux appliance, escalated to root, and then went after vCenter.
- Custom tooling. A Go tool Mandiant calls BONESAW created SSO admin accounts, copied the directory database, and stole the SAML signing key and vCenter secrets. Another, SAWSNAKE, forged SAML logins (Golden SAML), which means impersonating users and walking around MFA.
- Covering tracks. They turned on SSH on vCenter, took the master key and database credentials, and turned SSH back off.
- Reaching into guests. They pulled Active Directory database files straight off guest VM disks. When you own vCenter, the domain controllers are just files.
- Also on the list: a backdoored SSH server that logs passwords, JSP webshells, and a Slack-based backdoor from an earlier intrusion.
I'll repeat my standing disclosure: I work at Zscaler. I'm not going to pretend a cloud proxy patches your hypervisor. But this chain is the textbook argument for not letting management planes be reachable from anything but a handful of admin hosts. The attacker hopped from a remote support appliance to a Linux box to vCenter, all on the internal network. Every hop was "allowed" because it was inside.
What To Do
- Patch vCenter now to the fixed build for your branch. If you're on 7.0, call Broadcom today, not next sprint.
- Lock down port 2012 (the Directory Service RPC interface) and the rest of vCenter's management surface to dedicated admin hosts. If your user VLAN can reach vCenter, fix that this week.
- Hunt, don't just patch. Exploitation started in September. Look for SSO admin accounts you don't recognize, VAMI logs showing SSH enabled and then disabled, and odd SSH services on high ports from internal appliances.
- If you find anything, assume Golden SAML. Rotate the vCenter STS signing certificate and all SSO credentials, and treat Active Directory as exposed.
- Check your BeyondTrust Remote Support instances against CVE-2026-102764 if you haven't already. That was the front door here.
- Put EDR or at least logging on internal Linux appliances. The pivot point in this chain was a box nobody was watching.
Update, November 21: HOL reports that CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities catalog on November 20 with a federal remediation deadline of Monday, November 23. I couldn't open the KEV catalog directly to confirm, so check it yourself, but either way: that's a three-day clock. If you're a federal agency or anyone who follows KEV dates, this is a weekend patch. (HOL, Help Net Security)
Bottom Line
The hypervisor control plane is the keys to everything that runs on it, and it's been attacked as a zero-day for two months. Patch it, hide it, and go look for visitors who arrived in September.
Sources: Rapid7 on CVE-2026-123890, The Hacker News on ARMORY CASTLE, The Hacker News on the advisory, SecurityOnline, Google Threat Intelligence: ARMORY CASTLE Exploits vSphere