Broadcom patched zero-day CVE-2026-123890 in VMware vCenter (CVSS 9.8). The Armory Castle group has been exploiting the auth bypass since September 2026. How to defend.
What happened
On November 19, 2026, Broadcom released emergency security update VMSA-2026-0009, closing a critical vulnerability in VMware vCenter Server. The issue is tracked as CVE-2026-123890, scored CVSS 9.8 (Critical), and affects the VMware Directory Service (vmdird). The flaw lets an attacker with network access to vCenter bypass authentication and gain unauthorized access to the system with administrator privileges.
The key point: this is not a theoretical threat. Google Mandiant and Google Threat Intelligence Group confirmed the vulnerability was exploited in the wild as a zero-day since at least early September 2026 — almost two and a half months before the patch shipped. Broadcom treats the update as an emergency and urges organizations to apply it as soon as possible.
Why vCenter is the "keys to everything"
vCenter Server is the central management console for an entire VMware environment: ESXi hosts, virtual machines, networks, storage, accounts, and security policies. Whoever controls vCenter effectively controls the whole virtualized data center — they can create and delete VMs, take snapshots, change network settings, and above all read and exfiltrate data.
That is why APT groups value such vulnerabilities so highly: one successful authentication bypass opens a path to the entire corporate infrastructure built on VMware.
Technical details: how the authentication bypass works

The vulnerability is classified as CWE-288 — "authentication bypass using an alternate path or channel". According to Mandiant, successful exploitation creates a remote authenticated session established as the system administrator administrator@vsphere.local. With that session, an attacker can execute arbitrary commands and acquire files — including the data.mdb database — via the vmdirdbcp RPC interface of the vmdird directory service.
A CVSS score of 9.8 means the most dangerous combination: network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and high impact on confidentiality, integrity, and availability (C:H/I:H/A:H).
Importantly, the vulnerability exists regardless of whether Enhanced Linked Mode is enabled, and there is no official workaround. The only complete mitigation is upgrading to a fixed version.
Who is behind the attacks: Armory Castle (UNC5221 / Warp Panda)
Mandiant links exploitation of CVE-2026-123890 to Armory Castle — a suspected Chinese state-linked APT group previously tracked as UNC5221 and also known as Warp Panda. It was Mandiant that privately reported the vulnerability to Broadcom.
According to Mandiant, the attackers obtained initial access through CVE-2026-102764, a recently patched zero-day in BeyondTrust Remote Support. They then pivoted to Linux appliances on the internal network and targeted vCenter in early September 2026.
A notable detail: Mandiant has evidence that Armory Castle had knowledge of CVE-2026-123890 prior to the July 29, 2026 disclosure of CVE-2026-59309, a separate vCenter authentication bypass. The Bonesaw tool was used against vCenter servers already patched for CVE-2026-59309 — confirming this is a distinct, newer vulnerability.
The attack chain: from BeyondTrust to ESXi

The attack flow described by researchers looks like this:
- Initial access — via a zero-day in BeyondTrust Remote Support (CVE-2026-102764).
- Lateral movement across the network to Linux appliances and discovery of vCenter servers.
- Exploitation of CVE-2026-123890 via the custom Bonesaw tool — creating an administrator session as administrator@vsphere.local.
- Theft of the Lightning Memory-Mapped Database (LMDB) and extraction of SAML signing material.
- Creation of an SSO administrator account and installation of backdoors.
- Theft of the vCenter master encryption key and database credentials.
- Movement to an ESXi host and additional information extraction.
The end goal is persistent, stealthy access to the virtualized infrastructure and data theft, not a loud destructive attack. This is the classic tactic of espionage groups: work quietly and for a long time.
The attackers' tooling: Bonesaw, forged SAML tokens, and LMDB theft
The key tool in this campaign is Bonesaw. It exploits CVE-2026-123890, steals the LMDB database, extracts SAML signing material, and creates an SSO administrator account. A second tool then forges SAML tokens — allowing the attackers to authenticate as legitimate users even after the initial bypass has been closed.
This combination of an exploit, theft of cryptographic material, and token forgery makes the attack especially dangerous: simply updating vCenter may not remove backdoors that have already been installed, so a thorough compromise assessment is needed after patching.
Charles Carmakal, CTO of Mandiant, noted on LinkedIn that the company investigated multiple incidents involving Armory Castle's exploitation of CVE-2026-123890.
Affected versions and how to update
Broadcom released fixes on November 19, 2026. All vCenter versions prior to the "fixed" versions listed below are affected:
- VMware Cloud Foundation / vSphere Foundation 9.1.x.x — update to 9.1.1.0200
- VMware Cloud Foundation / vSphere Foundation 9.0.x.x — update to 9.0.2.0200
- VMware vCenter Server 8.0 — update to 8.0 U3m
- VMware Cloud Foundation 5.x — update to 5.2.5
- VMware Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 — update to 8.0 U3m (see KB463116)
- VMware Telco Cloud Infrastructure 3.0 — update to 8.0 U3m (see KB463116)
vCenter 7.0 has reached end of support: organizations with extended-support contracts should contact Broadcom directly. The updates are cumulative, meaning they contain all prior fixes.
In the same advisory, Broadcom also closes four additional vulnerabilities in VMware SDDC Manager and VMware Tools for Windows (CVE-2026-123891, CVE-2026-123892, CVE-2026-123893, CVE-2026-123894). So the whole VMware stack should be updated, not just vCenter.
How to defend

Since there is no official workaround, the primary step is to update immediately. Additionally, consider the following actions:
- Restrict network access to vCenter. The management interface should never be reachable from the internet and should be accessible only from a dedicated administrative network via VPN or a jump host.
- Check for suspicious accounts, especially in the vsphere.local domain, and new SSO administrators.
- Review logins from unusual IP addresses and atypical RPC calls to the vmdird service.
- If vCenter was exposed externally, run a compromise assessment rather than just installing the patch: look for backdoors and forged SAML tokens.
- Check whether corporate credentials have appeared in known breaches — you can do this for free with our breach check tool (/tools/breach-check).
- Isolate any ESXi hosts to which attackers may have moved after compromising vCenter.
For specialists who want to systematize their incident-response knowledge, we have prepared a cybersecurity learning collection (/blog/kiberbezpeka-navchannya).
Conclusion
CVE-2026-123890 is a clear example of how a critical vulnerability in an infrastructure management system turns into a months-long espionage campaign. An authentication bypass in vCenter gives attackers the keys to the entire virtualized infrastructure, while stolen SAML material and forged tokens let them persist even after the flaw is closed.
For organizations that rely heavily on VMware across banking, telecom, and government sectors, this is a direct signal: check whether vCenter is exposed externally and update without delay. If your vCenter is reachable from the internet, consider yourself in the danger zone.