A suspected China-linked espionage group exploited a critical VMware vCenter zero-day for more than 2 months before Broadcom released a patch, according to Google. Broadcom fixed the flaw, tracked as CVE-2026-123890, in a security advisory published November 19, 2026. On the same day, Google Threat Intelligence Group (GTIG) and Mandiant reported that the group it calls ARMORY CASTLE had used the bug in early September.
The flaw lets an attacker with network access to vCenter bypass authentication and get an administrator session. Broadcom rated it 9.8 out of 10 on the CVSS scale and said there is no workaround. vCenter 7.0, which is out of general support, has no public fix.

What Broadcom fixed
Broadcom’s advisory, VMSA-2026-0009, describes CVE-2026-123890 as an authentication bypass in the VMware Directory Service in vCenter. Broadcom credited Mandiant with reporting the flaw. The advisory does not say whether the bug has been exploited in the wild.
Fixed versions 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: 5.2.5
- vCenter 7.0: no public fix; Broadcom tells customers with extended support contracts to contact support
Telco Cloud Platform and Telco Cloud Infrastructure are also affected. The same advisory fixes 4 other bugs in SDDC Manager and VMware Tools for Windows. In its FAQ, Broadcom said the vCenter issue qualifies as an emergency change.
How the attackers reached vCenter
GTIG attributes the activity to ARMORY CASTLE, a suspected China-nexus espionage actor it formerly tracked as UNC5221. According to GTIG, the group first got in through CVE-2026-102764, a BeyondTrust Remote Support zero-day that Google described in October.
From the Remote Support appliance, the attackers moved to internal Linux appliances that had no endpoint detection and response (EDR) tools. They scanned the network for ports used by VMware services, including port 2012, which vCenter single sign-on (SSO) uses and which the exploit targets. GTIG said the group deployed 5 newly identified malware families and tools:
- SLIMSAVAGE and CAGEMATCH: web shells used to run commands and upload tools
- BONESAW: a Go exploit tool for
CVE-2026-123890that created an SSO administrator account and stole vCenter’s directory database - SAWSNAKE: a tool that can forge vCenter login tokens, letting attackers bypass multi-factor authentication and pose as any user
- BEARBONES: a backdoored SSH server that skips password checks
The group also used LAZYBONES, a backdoor that talks to its operators over Slack and that GTIG had seen in an earlier ARMORY CASTLE intrusion.
Once inside vCenter, GTIG said the attackers turned on SSH, stole the vCenter master encryption key and database credentials, then turned SSH off again. They then moved to an ESXi host, planted an SSH key on the root account and copied files from a guest virtual machine disk. GTIG has not named the victim or its sector.
Exploit predates an earlier vCenter flaw
Mandiant said it has evidence that ARMORY CASTLE knew about CVE-2026-123890 before Broadcom disclosed a different vCenter authentication bypass, CVE-2026-59309, on July 29, 2026. Logs show BONESAW was run in early September against a vCenter server that was already patched for the July bug. The recovered tool carries a build timestamp of July 13, 2026, though GTIG noted that such metadata can be changed.
Broadcom’s FAQ says the 2 flaws are distinct, so systems patched only for the July bug are still exposed.
Google has previously linked UNC5221 to the BRICKSTORM backdoor, which also features in reporting on Warp Panda’s attacks on VMware ESXi at law firms. China-linked groups have repeatedly gone after hypervisors and other systems that sit below normal endpoint security.
What defenders should do
GTIG urged organizations to apply Broadcom’s patches immediately. Because the attack can create admin accounts and steal signing keys, patching alone may not remove an attacker who is already inside. Teams should also:
- Check vCenter for unexpected SSO administrator or machine accounts created since early September
- Review logs for SSH being turned on and off through the appliance management interface
- Limit access to vCenter management ports, including 2012, to trusted admin systems only
- Consider rotating vCenter SAML signing certificates and SSO credentials if compromise is suspected
GTIG also published indicators of compromise, YARA rules and a vCenter hardening script with its report.












