Broadcom released emergency patches on November 19, 2026, for CVE-2026-123890, a critical unauthenticated authentication bypass in the VMware Directory Service of VMware vCenter Server. The flaw carried a CVSS score of 9.8 and allowed remote attackers with network access to obtain an authenticated session as administrator@vsphere.local without credentials. Google’s Mandiant and Threat Intelligence Group reported that the suspected China-linked actor Armory Castle had exploited the issue as a zero-day since early September 2026.
VMware vCenter Zero-Day Exploitation and Attack Details
The vulnerability resided in the VMware Directory Service component and required no user interaction. Attackers used a custom Golang tool named BONESAW to create an SSO admin account, exfiltrate the LMDB directory database, and extract SAML signing material. This access enabled further movement to ESXi hosts and virtual machine data. The campaign began with exploitation of a separate zero-day in BeyondTrust Remote Support before pivoting through internal Linux appliances.

Armory Castle, previously tracked as UNC5221 or Warp Panda, has a documented history of targeting virtualization infrastructure and edge devices for espionage. The group demonstrated prior knowledge of similar flaws disclosed in July 2026. Mandiant and GTIG published indicators of compromise, including YARA rules, on the same day as the Broadcom advisory. The activity has not yet appeared in the CISA Known Exploited Vulnerabilities catalog as of November 20, 2026.
Broadcom’s VMSA-2026-0009 advisory also addressed four additional CVEs affecting related components. These include a SQL injection in SDDC Manager rated 8.1, an authenticated command injection rated 7.2, a local privilege escalation rated 6.7, and a SAML token signature bypass in VMware Tools rated 6.7. No workarounds were provided for any of the issues.
Fixed Versions and Immediate Remediation Steps
Broadcom classified the update as an emergency change and listed fixed versions as vCenter 9.1.1.0200, 9.0.2.0200, and 8.0 U3m. VMware Cloud Foundation customers must apply version 5.2.5 through asynchronous patching, while Telco Cloud Platform updates follow guidance in KB463116. Older unsupported releases such as vSphere 6.5 and 6.7 remain exposed, and vCenter 7.0 receives extended support only with no public patch available.
Organizations running VMware environments should treat this update as a priority and restrict network access to vCenter management interfaces immediately. Administrators are advised to review the full response matrix in the advisory and apply patches across standalone vCenter instances as well as deployments within VMware Cloud Foundation, vSphere Foundation, and Telco Cloud Platform. Mandiant recommends hunting for BONESAW tool artifacts and unusual SSO account creation activity.
The incident underscores ongoing risks to virtualization management platforms that serve as central control points for enterprise infrastructure. Broadcom urges customers to monitor for additional public exploits and to validate patch deployment through standard change-management processes before broader rollout.
Frequently asked questions
Which versions of VMware vCenter receive patches for CVE-2026-123890?
Broadcom lists fixed versions as vCenter 9.1.1.0200, 9.0.2.0200, and 8.0 U3m. VMware Cloud Foundation moves to 5.2.5 via asynchronous patching.
How long was the VMware vCenter zero-day exploited before disclosure?
Mandiant reported exploitation by Armory Castle beginning in early September 2026, more than two months before the November 19, 2026 patches.
What other CVEs were addressed in the same Broadcom advisory?
VMSA-2026-0009 covers CVE-2026-123891 through CVE-2026-123894, including SQL injection in SDDC Manager and command injection issues.
What immediate actions should administrators take after the Broadcom patch release?
Apply the emergency updates without delay, restrict network access to vCenter, and scan for indicators of compromise using Mandiant YARA rules.
By YasTech Editorial
Comments 1