November 20, 2026

Spies Used a vCenter Zero-Day for Two Months Before the Patch Arrived. Your Questions on the VMware Emergency Fix, Answered

Broadcom has patched a critical authentication bypass in VMware vCenter, and Google says a suspected China-nexus espionage group was already exploiting it in early September to become vCenter administrator, forge sign-in tokens and steal data. Here are the questions IT teams are asking, and the answers.

A row of dark rack-mounted servers with glowing status lights in a dim data center aisle

If your company runs its servers as virtual machines on VMware, the console that manages all of them just became the most urgent item on the patch list. Broadcom published fixes on November 19 for a critical vCenter flaw, and a day later Google’s threat intelligence team and Mandiant revealed that an espionage group had been using it quietly for more than two months. The answers below are drawn from The Hacker News’ report on Google’s findings and its earlier coverage of Broadcom’s advisory.

What exactly is broken?

The bug, CVE-2026-123890, sits in the VMware Directory Service that vCenter uses for single sign-on. It is rated 9.8 out of 10. According to Google, someone who can reach the service over the network can trick it into disclosing a session key and end up with an authenticated session as administrator@vsphere.local, the built-in top-level account. No password is needed.

Who was exploiting it, and how?

Google attributes the attacks to a suspected China-nexus group it tracks as Armory Castle, formerly UNC5221. The group was not knocking on the front door. It first broke into a BeyondTrust Remote Support appliance using a separate flaw that was also a zero-day at the time (CVE-2026-102764), moved to an internal Linux appliance, gained root there, and then scanned for VMware-specific ports, including port 2012, the vCenter single sign-on control interface.

From there it used a custom Go tool Google calls BONESAW to exploit the vCenter bug, pull the directory database, take over the SAML token service and create its own single sign-on administrator. A second tool, SAWSNAKE, forged vCenter sign-in tokens, which Google says let the attackers bypass multi-factor authentication and impersonate any user. The group then created a local admin account, switched on SSH through the appliance management API, logged in, mounted the ESXi hosts’ storage volumes, planted an SSH key for the root account and carried data out through the compromised Remote Support appliance.

Is this the same as the vCenter bugs from the summer?

No. It is the second critical authentication flaw in the same directory component this year; an earlier one, CVE-2026-59309, was patched on July 29. It is also the second VMware zero-day linked to Armory Castle in 2026, after CrowdStrike reported the group abusing a low-severity ESX logging flaw to hide its tracks.

Which versions need the update?

vCenter 8.0, 9.0 and 9.1 are affected, along with the vCenter builds bundled in VMware Cloud Foundation (including the older 5.x line), vSphere Foundation and the Telco Cloud products. Fixed builds include 9.1.1.0200, 9.0.2.0200 and 8.0 U3m. Broadcom says versions past end of support, including vSphere 6.5 and 6.7, should be presumed affected, and vSphere 7.0 customers need an extended support contract to request a patch. ESX hosts themselves are not affected by this bug.

Is there a workaround if we cannot patch tonight?

Broadcom lists none, and its FAQ describes the update as qualifying as an emergency change. The update cannot be installed through vCenter Quick Patch. Virtual machines keep running while vCenter updates, but management access drops briefly. Teams in the middle of a Cloud Foundation upgrade should read the advisory first: installing 8.0 U3m or 9.0.2.0200 blocks a later move to VCF 9.1.1, so Broadcom suggests going to 9.1.1 first or waiting for 9.1.2.

We patched. Are we done?

Not necessarily. The exploitation began in early September, so a patch closes the hole but does not remove anyone who came through it. Based on the activity Google describes, things worth checking include unexpected single sign-on or local administrator accounts in vCenter, SSH switched on for the appliance when it should be off, new SSH keys on ESXi root accounts, and traffic to port 2012 from systems that have no business talking to it.

What this means for your company

Whoever controls vCenter controls every virtual server it manages, so treat it as one of your crown jewels. Patch it as an emergency, then confirm the management interfaces are reachable only from a small admin network rather than from every internal system, since this attack was launched from another appliance already inside. Check that remote support tools, VPNs and other edge appliances are patched too, because they were the first step here. Review vCenter and ESXi for accounts, SSH settings and keys you did not create, and make sure your backups of those virtual machines live somewhere a vCenter administrator cannot delete them. If you rely on a hosting provider or MSP for your VMware environment, ask them today when the fix was applied.

If you are unsure whether your virtualization platform is patched, segmented and backed up the way it should be, we can walk through it with you. Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.

About The Author