A suspected Chinese espionage group exploited a critical VMware vCenter Server flaw for more than two months before a patch existed, Google’s Mandiant reported as Broadcom released fixes. The bug, tracked as CVE-2026-123890 and scored CVSS 9.8, gives an unauthenticated attacker administrator access to vCenter.
Armory Castle Used CVE-2026-123890 Against vCenter Before Broadcom Had a Fix
Mandiant attributes the exploitation to Armory Castle, a suspected China-nexus espionage group that it formerly tracked as UNC5221 and that is also called Warp Panda. The activity began in early September, according to the researchers, well ahead of the patches Broadcom published in advisory VMSA-2026-0009. Mandiant CTO Charles Carmakal said the company investigated multiple incidents involving the exploitation. Broadcom’s advisory does not mention attacks in the wild.
CVE-2026-123890 is an authentication bypass in the VMware Directory Service, known as vmdird. Mandiant describes it as an unauthenticated SRP-6a session key disclosure over DCE/RPC that hands the attacker an authenticated session as administrator@vsphere.local.
How BeyondTrust Zero-Day CVE-2026-102764 Opened the Door
The intrusions did not begin at vCenter. Mandiant says initial access came through a zero-day in BeyondTrust Remote Support, tracked as CVE-2026-102764 with a CVSS score of 9.3. From there the attackers moved to an internal Linux appliance, escalated to root, and scanned for VMware-related ports 9080, 5480 and 2012 before targeting vCenter itself.
BONESAW and BARECLAW Tooling Found in the Intrusions
Once on vCenter, the attackers ran a Golang utility called BONESAW. According to Mandiant, it exploits the flaw to exfiltrate the LMDB directory database, hijack the SAML Security Token Service and create an SSO administrator account. A second tool forged SAML tokens, and the attackers also took the vCenter master encryption key and database credentials. Mandiant identified a proxy tunneler named BARECLAW and six malware families and utilities in total.
The group then enabled SSH through the VAMI API and created a local administrator account on vCenter. It moved on to ESXi hosts, mounting VMFS volumes, adding an SSH key to root’s authorized_keys file and stealing data.
Evidence Suggests the Attackers Knew of the Bug Before an Earlier vCenter Disclosure
Mandiant says Armory Castle likely knew of the flaw before the July 29 disclosure of a separate vCenter bypass, CVE-2026-59309. The BONESAW binary carries a July 13 build timestamp, though the researchers caution that such metadata can be altered. BONESAW was also used against a vCenter server that had already been patched for CVE-2026-59309, which shows the newer flaw was a distinct route in.
Patched Releases and the Unpatched vCenter 7.0 Gap
Broadcom fixed the flaw in vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m. Exploitation was observed against vCenter 7.x and 8.x, and the affected products also include SDDC Manager and VMware Tools for Windows. No public patch exists for vCenter 7.0, which passed the end of general support in October 2025, leaving those deployments without a fix for a flaw already used in attacks.
Mandiant urges organizations to patch and also examine their systems for signs of compromise, since the activity predates the fix by roughly ten weeks. Because the attackers stole the SSO signing material and the vCenter master encryption key, installing the update does not by itself remove access that was already obtained through forged SAML tokens or created administrator accounts.
Control of vCenter Extends to Every Virtual Machine It Manages
A successful compromise gives the attacker full administrative control of vCenter and the virtual machines it manages, along with the credentials and signing material that protect that environment. The chain from a remote-support zero-day to a virtualization management plane, then down to ESXi hosts, illustrates how a single unpatched edge product can expose an entire virtual estate. Broadcom’s advisory carries no exploitation warning, so defenders reading only the vendor bulletin would have no signal that the flaw was under active use.
