What happened. Broadcom on Thursday, Nov 19 published advisory VMSA-2026-0009, fixing CVE-2026-123890 in VMware vCenter Server, rated 9.8 out of 10. The same day, Google Threat Intelligence Group and Mandiant said a suspected China-nexus espionage group it tracks as Armory Castle (formerly UNC5221; SecurityWeek notes it is also called Warp Panda) had already exploited the bug in early September, more than two months before a fix existed. Mandiant reported the flaw to Broadcom. Mandiant CTO Charles Carmakal said on LinkedIn the firm has investigated multiple incidents tied to it.
The bug, in plain words. vCenter is the control panel that runs a company’s VMware servers and virtual machines. The flaw sits in its built-in directory service, which handles logins. Over the network on port 2012, an attacker with no password can pull out a shared session key and use it to open a session as administrator@vsphere.local, the top admin account. From there, Google says, they can run commands and copy the directory’s database file.
How the attack ran. Google says Armory Castle first got in through CVE-2026-102764, the BeyondTrust Remote Support zero-day it disclosed in October. The group then moved to internal Linux appliances that had no endpoint detection (EDR) tools, scanned for VMware ports, and used a custom Go tool Google calls BONESAW to exploit vCenter. BONESAW stole the login database, took the signing material behind vCenter’s single sign-on (SAML, the system that issues login tokens) and created a new SSO administrator account. A second tool forged login tokens, and the group dropped several new backdoors and web shells. SecurityWeek, citing Google, says the attackers also took the vCenter master encryption key and database credentials, then moved on to an ESXi host. Google says BONESAW was used against a vCenter that was already patched for CVE-2026-59309, a separate login bypass disclosed in July.
Who is affected. Broadcom’s fixes are vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m. Mandiant says BONESAW works against vCenter 7.x and 8.x, and SecurityWeek reports there is no public patch for 7.0, which reached end of general support in October 2025. SecurityWeek says Broadcom’s advisory, which also fixes four SDDC Manager and VMware Tools flaws, does not mention in-the-wild exploitation; the exploitation evidence comes from Google.
Why it matters. vCenter holds the keys to every virtual machine it manages, so an admin session there is close to owning the data center. This is also the same actor and the same entry point as October’s BeyondTrust case, which shows how one remote-access appliance can become a path to the hypervisor layer. Security appliances and virtualization consoles usually can’t run EDR, which is exactly where this group lived.
Defender takeaway. Patch vCenter now, and treat 7.x as an urgent upgrade. Then hunt, because the bug was in use for months: look for SSO administrator accounts nobody created, rotate SSO/SAML signing certificates and service credentials if anything looks off, and restrict ports 2012, 5480 and 22 on vCenter to a short allow-list of admin workstations. Google advises not relying on the appliance’s built-in firewall alone. Worth asking your team: which of our internal systems can reach vCenter’s management ports today, and would we notice a new SSO admin?
