SecureCyberVM
CVE Lookup Daily Threat Briefing Exploited CVEs Ransomware Zero-day
SecureCyberVM
Get the Patch Brief
Zero-Day Critical

VMware Patches vCenter Zero-Day Exploited by China-Nexus Group Since September

Broadcom has patched CVE-2026-123890, a critical vCenter authentication bypass that Mandiant says a suspected China-nexus espionage group exploited as a zero-day since early September.

VMware Patches vCenter Zero-Day Exploited by China-Nexus Group Since September

Broadcom has released security updates for VMware vCenter Server that fix CVE-2026-123890, an authentication bypass in the VMware Directory Service that Google’s Mandiant says a suspected China-nexus espionage group exploited as a zero-day from early September 2026. Broadcom rates the flaw critical with a CVSS 3.1 base score of 9.8 and lists no workaround.

The fix ships in advisory VMSA-2026-0009, published on November 19 and revised on November 20, which also covers four lower-severity flaws in VMware SDDC Manager and VMware Tools for Windows. Mandiant, which reported the vCenter bug to Broadcom, published its own analysis of the intrusions together with indicators of compromise and detection rules.

What happened

According to Mandiant and Google Threat Intelligence Group, the actor tracked as ARMORY CASTLE (formerly UNC5221) used a custom tool Mandiant calls BONESAW to exploit the flaw. Mandiant describes the issue as unauthenticated disclosure of a Secure Remote Password session key over DCE/RPC, caused by predictable UUID generation in the directory service’s SRP interface. The result, Mandiant says, is an authenticated session as [email protected], which allowed the attackers to create an SSO administrator account and take files including the directory database.

Mandiant says forensic evidence shows exploitation in early September 2026, and that BONESAW was run against a vCenter appliance that was already patched for CVE-2026-59309, an earlier vCenter flaw disclosed on July 29. Broadcom states that CVE-2026-123890 is a new and distinct issue. Mandiant found the activity while investigating an intrusion that began with the BeyondTrust Remote Support zero-day CVE-2026-102764, which it reported in October.

Broadcom’s advisory credits Mandiant with the report but does not itself state that the flaw was exploited in the wild, a point BleepingComputer also noted. Post-exploitation tooling described by Mandiant includes the SLIMSAVAGE and CAGEMATCH web shells and the SAWSNAKE, BEARBONES and LAZYBONES implants.

Who is affected

Broadcom lists vCenter Server versions below the fixed releases as affected, whether deployed standalone or as part of VMware Cloud Foundation, vSphere Foundation, Telco Cloud Platform or Telco Cloud Infrastructure. Fixed versions include:

  • vCenter 9.1.x: 9.1.1.0200
  • vCenter 9.0.x: 9.0.2.0200
  • vCenter 8.0: 8.0 U3m (Cloud Foundation 5.x customers are also directed to SDDC Manager 5.2.5)
  • Telco Cloud Platform and Telco Cloud Infrastructure: see Broadcom KB463116

For vCenter 7.0, Broadcom tells customers with extended support contracts to contact support; no public fix is listed. Mandiant says BONESAW achieves full compromise of both 7.x and 8.x appliances, and Broadcom’s Q&A says vSphere 6.5 and 6.7 should be presumed affected. ESXi, NSX, Workstation and Fusion are not affected, according to Broadcom.

The other four flaws are CVE-2026-123891 (SDDC Manager SQL injection), CVE-2026-123892 (SDDC Manager authenticated command injection), CVE-2026-123893 (SDDC Manager local privilege escalation) and CVE-2026-123894 (a SAML token signature bypass in VMware Tools for Windows, fixed in Tools 13.1.5.0 and 12.5.5).

Severity and exploitation

Broadcom gives CVE-2026-123890 a 9.8 score: network-reachable, no privileges or user interaction required. Mandiant reports that exploitation targets the directory service RPC port, TCP 2012. Broadcom rates the SDDC Manager SQL injection and command injection flaws as important and the remaining two as moderate. No exploitation of those four has been reported. Whether CISA has added the vCenter flaw to its Known Exploited Vulnerabilities catalog was not stated in the sources reviewed.

Because the attackers were active for roughly two and a half months before a patch existed, installing the update does not by itself establish that an appliance is clean.

What defenders should do now

  1. Upgrade vCenter to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m as applicable, and SDDC Manager to the fixed release for its branch. Broadcom says there is no workaround.
  2. For vCenter 7.0 and older appliances, contact Broadcom support, prioritize migration, and restrict network access to vCenter management and directory ports in the meantime.
  3. Limit inbound access to vCenter, including TCP 2012, to administrative networks, and apply egress filtering on the appliance. Mandiant points to its VCSA hardening tool for this, with a recommendation to test before production use.
  4. Hunt for compromise using Mandiant’s published indicators: unexpected SSO administrator accounts in vsphere.local, files such as /tmp/123, /tmp/sss, /tmp/dbr and /usr/bin/vmtoolscs, unknown JSP files on the appliance, SSH being enabled through the appliance management API, and hidden directories on VMFS datastores.
  5. Check logs for connections from the network addresses Mandiant lists and deploy its published YARA rules.
  6. Update VMware Tools on Windows guests to 13.1.5.0 or 12.5.5.
  7. If compromise is suspected, treat the SSO domain as breached: rotate vCenter and SSO credentials and review ESXi hosts managed by the appliance.

SCVM analysis

This is the second time in 2026 that vCenter’s directory service has been at the center of a serious authentication flaw, and Mandiant’s finding that the attackers ran their tool against a host already patched for the July bug shows that patching against the last disclosure does not protect against an actor still holding an undisclosed one. vCenter controls an organization’s whole virtual estate and is rarely watched by endpoint security tools, which makes it attractive to espionage groups that want to stay hidden for months. Organizations should treat vCenter as a tier-zero asset: keep it off general networks, send its logs to central monitoring, and assume that any appliance reachable by an attacker since September needs a compromise assessment, not just an update. The lack of a public fix for vCenter 7.0 leaves organizations still running it exposed.

Sources

About this article: produced by the SCVM Newsroom with AI assistance from the public sources linked above, enriched with NVD, FIRST EPSS and CISA KEV data, and checked by automated quality controls under our editorial policy. Spotted an error? Request a correction.

SecureCyberVM

Install SecureCyberVM

Get the Daily Threat Briefing and exploited-CVE alerts one tap away, full screen, like an app.