enzosoler.comreviews 09bench 9 deviceslive test Can a ring and a watch replace my Apple Watch?
Published

VMware vCenter flaw CVE-2026-123890 was exploited before the patch. Update to 8.0 U3m and check for SSO admin accounts

A row of black server racks with mesh doors and red and blue network cables in a data center
Image: Pexels

Broadcom patched CVE-2026-123890 (CVSS 9.8), an authentication bypass in vCenter's directory service, on November 19. Google says a China-linked group used it as a zero-day in early September to become administrator@vsphere.local and forge SAML tokens. Fixes: vCenter 8.0 U3m, VCF 5.2.5 and VCF 9 builds. No workaround exists.

If your company runs VMware vCenter, patch it this week. Broadcom fixed CVE-2026-123890 on November 19, and Google’s threat intelligence team says a suspected China-linked group was already using it as a zero-day in early September. Broadcom lists no workaround, so the update is the only fix.

What the flaw does

CVE-2026-123890 is rated CVSS 9.8, according to The Hacker News. It sits in the VMware Directory Service (vmdird) on the vCenter appliance. Google Threat Intelligence Group and Mandiant describe it as an unauthenticated session key disclosure in the service’s RPC interface on port 2012. An attacker who can reach that port, without a password, gets a session as administrator@vsphere.local, the top account in vSphere.

The fix is part of Broadcom advisory VMSA-2026-0009, which also patches three SDDC Manager flaws and a SAML signature bypass in VMware Tools for Windows (CVE-2026-123894).

Which versions fix it

Product Fixed in
vCenter 8.0 (vSphere 8) 8.0 U3m
VMware Cloud Foundation 5.x 5.2.5 (vCenter 8.0 U3m)
VCF and vSphere Foundation 9.1.x 9.1.1.0200
VCF and vSphere Foundation 9.0.x 9.0.2.0200
vCenter 7.0 Contact Broadcom Support (extended support only)
VMware Tools for Windows 13.1.5.0, or 12.5.5 for 12.x and 11.x

The 9.x builds are as reported by The Hacker News from the advisory. Broadcom’s own Q&A for VMSA-2026-0009 says vSphere 6.5 and 6.7 should be presumed affected, since Broadcom no longer evaluates them. It also warns that 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1, and tells teams in the middle of that upgrade to wait for 9.1.2. ESX hosts, NSX, Workstation and Fusion are not affected.

How the attackers used it

Google tracks the group as ARMORY CASTLE, formerly UNC5221. In the intrusion it describes, the attackers first got in through a BeyondTrust Remote Support appliance (CVE-2026-102764, since patched), scanned for vCenter’s ports, then used the vmdird flaw to log in as the vSphere administrator. From there, according to Google:

  1. They copied vCenter’s directory database with a tool Google calls BONESAW and created a new SSO administrator account.
  2. They took over the SAML signing service, which let them forge login tokens that skip multi-factor authentication.
  3. They created a local admin account, switched on SSH through the appliance management API, and planted a backdoor on TCP port 33992.
  4. On ESXi hosts, they mounted datastores, added an SSH key for root, and copied data out.

Google describes this as targeted espionage, and says the tool’s build date of July 13 suggests it was made for wider use. Treat that last point as Google’s inference.

Patching alone does not evict an intruder

Our read: the patch closes the door, but the attack path creates accounts and signing access that survive an update. If vCenter was reachable from a network an attacker could touch since September, check before you call it done.

  1. Update first. Move to the fixed build in the table above. There is no configuration change that blocks the flaw.
  2. Limit port 2012. The flaw is reached on vCenter’s directory port. Only your ESXi hosts and admin workstations should reach the appliance. Mandiant’s free VCSA hardening tool applies inbound and outbound firewall rules on the appliance itself.
  3. List every SSO and local admin account on vCenter and remove any you can’t name an owner for.
  4. Look for SSH being switched on. Google’s detection guidance flags the API call PUT /rest/appliance/access/ssh. If you see it and nobody on your team made it, treat the environment as compromised.
  5. Check ESXi hosts for unknown root SSH keys and anything listening on port 33992.
  6. Patch the way in, too. If you run BeyondTrust Remote Support, confirm it has the fix for CVE-2026-102764.

If you find signs of the intrusion, rotating the vCenter SAML signing certificate matters as much as the patch, because forged tokens work as long as that key does. Bring in an incident response firm before you start removing things.

The same week, CISA flagged another exploited infrastructure flaw: Puppet Server CVE-2026-115731, which lets an attacker take over the server that pushes configuration to every managed machine.

One email when a review goes up. Unsubscribe from any of them.