Overview
Google says a suspected China-linked espionage group exploited a critical VMware vCenter authentication bypass, CVE-2026-123890 (CVSS 9.8), as a zero-day for more than two months before Broadcom released a patch. Mandiant reported the bug to Broadcom and attributes the activity to Armory Castle, formerly tracked as UNC5221 and also known as Warp Panda.
The flaw sits in the VMware Directory Service. A remote, unauthenticated attacker can obtain an authenticated session with administrator privileges.
What Mandiant observed
- Initial access: the group got in through CVE-2026-102764, a recently patched BeyondTrust Remote Support zero-day.
- Pivot: attackers moved to Linux appliances on the internal network, then targeted vCenter in early September.
- Tooling: a custom tool named Bonesaw exploited CVE-2026-123890. A second tool forged SAML tokens.
- Credential theft: they stole the Lightning Memory-Mapped Database (LMDB), extracted SAML signing material, and created a single sign-on administrator account.
- Further access: they took the vCenter master encryption key and database credentials, then moved to an ESXi host and extracted more data.
- Backdoors were installed. Mandiant has investigated multiple incidents.
Mandiant also has evidence the group knew of CVE-2026-123890 before the July 29, 2026 disclosure of CVE-2026-59309, a separate vCenter authentication bypass. Bonesaw was used against a vCenter server already patched for that earlier bug, so patching CVE-2026-59309 alone was not enough.
Affected and fixed versions
| Product line | Status |
|---|---|
| vCenter 9.1 | Fixed in 9.1.1.0200 |
| vCenter 9.0 | Fixed in 9.0.2.0200 |
| vCenter 8.0 | Fixed in 8.0 U3m |
| vCenter 7.x | Bonesaw works against it; no public patch. 7.0 left general support in October 2025 |
Broadcom's advisory also fixes four SDDC Manager and VMware Tools flaws and does not mention in-the-wild exploitation.
Recommended actions
- Apply the fixed vCenter builds listed above now.
- Hunt for compromise, not just patch. Mandiant CTO Charles Carmakal urges defenders to examine systems for evidence of intrusion.
- Look for unexpected SSO administrator accounts, new or altered SAML identity providers, and unusual access to vCenter database and key material.
- If compromise is suspected, rotate vCenter SSO signing certificates, the master encryption key, database credentials and ESXi credentials.
- Move vCenter 7.x to a supported version, and keep vCenter management interfaces off untrusted networks.
- Patch BeyondTrust Remote Support if you run it, as it was the entry point here.
