
Broadcom released emergency security updates on November 19, 2026, to close CVE-2026-123890, a critical authentication bypass vulnerability in VMware vCenter Server that threat intelligence researchers say has been exploited in zero-day intrusions since early September. Published under advisory VMSA-2026-0009 and detailed in reporting by BleepingComputer, the release also resolves four additional vulnerabilities affecting VMware SDDC Manager and VMware Tools for Windows. While Broadcom did not confirm active exploitation in its advisory, Google's Mandiant and the Google Threat Intelligence Group (GTIG) documented a multi-stage campaign linking the flaw to Armory Castle, a suspected Chinese state-sponsored espionage group previously tracked as UNC5221.
Emergency Patch Scope Across VMware Virtualization Stacks
According to Broadcom's advisory, CVE-2026-123890 affects any deployment running unpatched versions of VMware vCenter prior to the fixed builds specified in VMSA-2026-0009. The exposure extends across both standalone vCenter and SDDC Manager installations as well as integrated enterprise suites, including VMware Cloud Foundation, VMware vSphere Foundation, VMware Telco Cloud Platform, and VMware Telco Cloud Infrastructure. Windows virtual machines running vulnerable builds of VMware Tools are also covered by the broader VMSA-2026-0009 patch bundle.
Crucially, Broadcom confirmed that Enhanced Linked Mode configuration status does not protect vCenter instances from CVE-2026-123890. Any unauthenticated attacker with network reachability to a vulnerable vCenter Server can trigger the authentication bypass and obtain administrative privileges over the management plane, enabling direct control over hosted virtual machines. Broadcom classified the vCenter patch as an emergency update and urged operators to apply fixes immediately.
Directory Service Architecture and the BONESAW Exploitation Chain
Technical findings published by Mandiant and GTIG pinpoint the vulnerability inside the VMware Directory Service (vmdird). Successful remote exploitation bypasses authentication checks and establishes an authenticated session under the high-privilege [email protected] identity. Once inside that administrative context, an attacker can invoke the vCenter Server Directory Service RPC interface, vmdirdbcp, to execute arbitrary commands and exfiltrate sensitive server files, including the core data.mdb directory database.
Mandiant's investigation indicates that CVE-2026-123890 was not exploited in isolation, but rather as the second zero-day stage in a coordinated intrusion sequence. Armory Castle first breached target networks using CVE-2026-102764, a zero-day vulnerability in BeyondTrust Remote Support appliances exploited since late August 2026. From compromised BeyondTrust devices, the operators moved laterally onto internal Linux systems, planted SLIMSAVAGE web shells to preserve access, escalated privileges to root, and scanned internal subnets for VMware management servers. To compromise vCenter, the group deployed BONESAW, a custom Golang exploitation tool built to weaponize CVE-2026-123890.
Golden SAML Persistence and Lateral Movement Into Hypervisors
Once BONESAW established administrative access on a vCenter Server, the tool automated several post-exploitation actions designed for long-term persistence and identity theft. Mandiant observed BONESAW creating rogue vCenter Single Sign-On (SSO) administrator accounts, stealing the data.mdb directory database for offline credential extraction, and harvesting SAML signing keys from the compromised server.
Armed with stolen SAML signing keys, Armory Castle deployed a secondary tool named SAWSNAKE to conduct Golden SAML attacks. By forging valid authentication tokens, SAWSNAKE enabled the intruders to bypass multifactor authentication controls and impersonate legitimate administrators. Alongside SAWSNAKE, the group installed multiple custom web shells and backdoors—tracked as CAGEMATCH, BEARBONES, and LAZYBONES—to issue commands, transfer files, and harvest credentials. This control over the virtualization management plane allowed the attackers to reach underlying ESXi hosts and extract sensitive files directly from virtual machines, including Windows Active Directory databases.
Operational Impact on Enterprise Infrastructure and Security Workflows
For enterprise infrastructure and security teams, chaining an edge remote-support zero-day with a vCenter directory bypass poses an acute architectural risk. Because vCenter orchestrates hypervisors, storage, and guest virtual machine lifecycles, losing control of [email protected] exposes the entire virtualized estate—even when guest operating systems maintain strict local patching. Moreover, SAML key theft means that applying VMSA-2026-0009 alone will not evict an adversary who has already forged Golden SAML tokens or planted CAGEMATCH, BEARBONES, and LAZYBONES backdoors.
Incident response workflows in affected environments must therefore extend beyond standard patch deployment. Administrators need to inspect BeyondTrust Remote Support appliances for late-August compromises, hunt Linux management hosts for SLIMSAVAGE web shells, audit vCenter SSO administrator lists for unauthorized accounts, and rotate SAML signing keys alongside Active Directory credentials if data.mdb or guest VM disks may have been accessed.
Remediation Caveats, Attribution Boundaries, and Exposure Limits
Broadcom stated that no official workarounds exist for CVE-2026-123890 or the companion flaws in VMSA-2026-0009, advising organizations that cannot patch immediately to tighten network access controls and firewall rules restricting reachability to vCenter management interfaces. Additionally, Broadcom's advisory does not independently confirm in-the-wild exploitation, leaving the September 2026 timeline and Armory Castle attribution supported by Mandiant and GTIG threat intelligence rather than vendor forensics.
Mandiant notes that Armory Castle previously targeted enterprise edge appliances such as Citrix NetScaler and Ivanti Connect Secure, underscoring the group's focus on network and virtualization infrastructure. Organizations running VMware Cloud Foundation, vSphere Foundation, or Telco Cloud deployments should verify exact fixed build numbers across vCenter, SDDC Manager, and Windows VMware Tools in Broadcom's advisory to ensure all five patched flaws are resolved.
Automated Vertex AI (gemini-4-hydrogen) primary-source report; reviewed 2026-11-20.


