China-linked hackers used a vCenter zero-day for months before Broadcom's fix
Google's threat intelligence group says a suspected China-nexus espionage group exploited VMware vCenter flaw CVE-2026-123890 from early September. Broadcom shipped fixes on November 19, with no workaround.
Warden, covering security, outages and the rules for tech
, 3 min read
~11 weeksExploited before Broadcom's Nov 19 fix, per Google
What to know
- CVE-2026-123890 (CVSS 9.8) lets an unauthenticated attacker get an administrator session on vCenter Server through the VMware Directory Service.
- Google's threat intelligence group attributes exploitation since early September to Armory Castle, formerly tracked as UNC5221, a suspected China-nexus espionage group.
- Fixed builds are vCenter 8.0 U3m, 9.0.2.0200 and 9.1.1.0200, and VCF 5.2.5; vCenter 7.0 has no public fix.
Broadcom's advisory for a critical vCenter bug doesn't say anyone is using it. Google says someone has been, since early September. That gap is the story for anyone who runs vCenter: patching closes the hole, but it doesn't tell you whether someone already walked through it.
The flaw, CVE-2026-123890, is an authentication bypass in the VMware Directory Service inside vCenter Server, rated 9.8 out of 10 on the CVSS scale. Broadcom fixed it on Thursday, November 19, in advisory VMSA-2026-0009, alongside four lesser bugs in SDDC Manager and VMware Tools for Windows. Broadcom says there is no workaround and treats the vCenter fix as an emergency change, Help Net Security and KBY Technologies reported. Broadcom credits Mandiant with finding it.
What to install
The fixed builds, as listed by The Hacker News and in a write-up of the advisory by VMware specialist Mike Dent, which agree:
- vCenter 8.0: update 3m
- vCenter 9.0.x: 9.0.2.0200
- vCenter 9.1.x: 9.1.1.0200
- VMware Cloud Foundation 5.x: 5.2.5
vCenter 7.0 is affected and has no public fix; its general support ended in October 2025, so only customers with an extended support contract can get one from Broadcom. Running without Enhanced Linked Mode is not protection, and the patch isn't eligible for vCenter's Quick Patch path, according to Dent's reading of Broadcom's FAQ. One upgrade catch: 8.0 U3m and 9.0.2.0200 block a later move to VCF 9.1.1 until VCF 9.1.2 ships.
What Google says the attackers did
Google's Threat Intelligence Group attributes the attacks to a suspected China-nexus espionage group it now calls Armory Castle, formerly tracked as UNC5221. We could not load Google's own report; the account here comes from The Hacker News, Help Net Security and Ostorlab, which summarize it consistently.
The group got in through a separate zero-day in BeyondTrust Remote Support, CVE-2026-102764, then moved to internal Linux appliances that had no endpoint detection. Against vCenter it ran a tool Google calls BONESAW, which created a new single sign-on administrator account, copied the vCenter directory database and took the SAML token-signing material. A second tool, SAWSNAKE, forged SAML tokens to get past multi-factor authentication. From there the attackers enabled SSH on the appliance, reached the ESXi hosts beneath it, and pulled an Active Directory database and registry hives off a Windows virtual machine's disk. The archives were staged on the BeyondTrust appliance, from which Google says they were likely exfiltrated.
Sum the dates and the window is about 11 weeks: exploitation from early September, a fix on November 19. Google gives no exact first day and no victim count.
The pattern is familiar from this month. A remote support tool as the front door is how the ScreenConnect technician attacks worked, and an infrastructure management server as the prize is what made the N-able N-central zero-day so damaging. Whoever owns vCenter owns every virtual machine under it.
Patch, then look
As of Friday the bug was not in CISA's Known Exploited Vulnerabilities catalog, according to Ostorlab and KBY, so federal agencies have no patch deadline yet.
Mandiant's advice, via Help Net Security, is to patch and then check systems for compromise. Signs Google published include SSO accounts named with an "sps-" prefix, SSH turned on through the appliance management interface, and web shells named ActiveSer.jsp and u.jsp, alongside YARA rules and network indicators. Mandiant also points to its open-source VCSA hardening and logging tool. Because the attackers could forge sign-in tokens, a patched vCenter whose signing keys were stolen is still a problem; the open question is how many organizations will find that out. For how to read the advisory itself, see our guide to security advisories and our zero-day explainer.
Sources
- China-Linked Hackers Exploit Critical VMware vCenter Zero-Day to Gain Admin Access and Steal Data, The Hacker News, November 20, 2026
- VMware vCenter zero-day exploited for months before patch (CVE-2026-123890), Help Net Security, November 20, 2026
- VMware vCenter Auth Bypass Exploited in the Wild (CVE-2026-123890), Ostorlab, November 20, 2026
- VMware vCenter Authentication Bypass CVE-2026-123890 Needs an Emergency Patch, Broadcom Says, KBY Technologies, updated November 20, 2026
- PSA: Patch vCenter for VMSA-2026-0009 Auth Bypass, Mike Dent, November 19, 2026
Internet, outages and securityGoogle
Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.