VMware vCenter CVE-2026-123890 Zero-Day: What to Do
TL;DR · the short version
Broadcom fixed CVE-2026-123890, a CVSS 9.8 authentication bypass in the VMware Directory Service in vCenter, on 19 November 2026 (VMSA-2026-0009): vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, and VMware Cloud Foundation 5.2.5. There is no workaround, and vCenter 7.0 customers need Broadcom Support. The same day, Google Threat Intelligence Group and Mandiant said a suspected PRC-nexus espionage actor they call ARMORY CASTLE (formerly UNC5221) exploited the flaw in early September 2026, more than two months before the fix. Google says the group got in through a BeyondTrust Remote Support zero-day, then used a custom tool, BONESAW, to copy vCenter's directory database, steal the token-signing key, forge administrator logins and create an SSO administrator account, before reaching ESXi hosts and copying data from virtual machine disks. Broadcom's advisory does not itself say the flaw is exploited, and it was not in CISA KEV as of 20 November. Patch vCenter now, restrict who can reach it, and treat an unpatched, reachable vCenter as possibly compromised.
A China-linked espionage group exploited a critical VMware vCenter flaw for more than two months before it was patched, according to Google. Broadcom fixed CVE-2026-123890, an authentication bypass in the VMware Directory Service in vCenter rated CVSS 9.8, on 19 November 2026 in VMSA-2026-0009. The same day, Google Threat Intelligence Group (GTIG) and Mandiant said ARMORY CASTLE, which Google calls a suspected PRC-nexus espionage actor (formerly UNC5221), exploited it in early September 2026, used it to create a vCenter administrator account and went on to reach ESXi hosts. Broadcom credits Mandiant with reporting the flaw; its advisory does not itself say the flaw is exploited. There is no workaround.
Who this is for: CISOs, infrastructure and virtualisation owners, and vulnerability-management and incident-response leads running vCenter, vSphere Foundation or VMware Cloud Foundation.
Based on Broadcom's advisory and FAQ, the CVE record, the CISA KEV catalog and Google's report, read on 20 November 2026. PlayCISO is not affiliated with Broadcom, VMware, Google or Mandiant. We publish no exploit details or indicators; Google's report carries the indicators and detection rules.
Confirmed vs not yet known
Broadcom confirms: CVE-2026-123890 is an authentication bypass in the VMware Directory Service in vCenter, CVSS 3.1 9.8, reachable over the network without credentials; fixed builds for vCenter 9.1, 9.0 and 8.0 and VCF 5.x; no workaround; vSphere 7 is affected; ESX itself is not affected. It credits Mandiant with the report.
Google and Mandiant say: ARMORY CASTLE exploited the flaw in early September 2026 (from forensic evidence), after entering through a BeyondTrust Remote Support zero-day; it stole vCenter's token-signing key, database credentials and master encryption key, created administrator accounts, deployed webshells and backdoors, and reached ESXi hosts.
Attribution: Google's wording is "suspected PRC-nexus espionage actor". That is an assessment, not a confirmation.
Not known: the victim, its sector, how many organisations were hit, and whether anyone other than ARMORY CASTLE has the exploit. Broadcom does not state exploitation, and the flaw was not in CISA KEV as of 20 November.
Affected and fixed versions
From Broadcom's VMSA-2026-0009 and the CVE record. Update to the fixed build for your line, or later:
| Product and line | Fixed in |
|---|---|
| vCenter 9.1.x (VCF / vSphere Foundation) | 9.1.1.0200 |
| vCenter 9.0.x (VCF / vSphere Foundation) | 9.0.2.0200 |
| vCenter 8.0 | 8.0 U3m |
| VMware Cloud Foundation 5.x | 5.2.5 |
| vCenter 7.0 | Affected. Contact Broadcom Support if you have an extended support contract |
| Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2; Telco Cloud Infrastructure 3.0 | See Broadcom KB463116 |
- Severity: CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N), Critical. No credentials and no user interaction needed.
- Workaround: none listed. Broadcom's FAQ says other mitigations may exist in your environment but that relying on them is your decision.
- Older versions: the FAQ says vSphere 7 is affected and that it reached end of general support on 2 October 2025; it advises assuming older versions not listed in the advisory are affected.
- ESXi: the FAQ says ESX is not affected by this advisory. The fix is a vCenter update; see below for why ESXi still matters.
- Same advisory: VMSA-2026-0009 also fixes four lower-rated flaws in SDDC Manager (CVE-2026-123891, -123892, -123893) and VMware Tools for Windows (CVE-2026-123894). Apply those too.
How the intrusion worked, per Google
Everything in this section is Google's account in "ARMORY CASTLE Exploits vSphere", kept at the level defenders need.
- Way in: the group already had a foothold from a BeyondTrust Remote Support zero-day, CVE-2026-102764 (fixed in BeyondTrust BT26-05, in CISA KEV since 16 October). From there it scanned internally for VMware management ports.
- The vCenter flaw: Google describes CVE-2026-123890 as an unauthenticated flaw in the directory service's authentication interface, reached over its RPC port (TCP 2012), that yields an authenticated administrator session.
- BONESAW: a custom Go tool for vCenter 7.x and 8.x. Google says it copied the directory database for offline parsing, extracted the key vCenter uses to sign SAML login tokens, created a backdoor machine account, forged administrator tokens, granted itself Global Administrator and created an SSO administrator account.
- On the appliance: the group enabled SSH through the appliance management API, created a local administrator, took the vCenter master encryption key and database credentials, and disabled SSH afterwards. Google names two JSP webshells (SLIMSAVAGE, CAGEMATCH), a backdoored SSH server (BEARBONES), a token-forging tool used for "Golden SAML" logins that bypass MFA (SAWSNAKE, deleted after use) and a backdoor that uses Slack for command and control (LAZYBONES).
- ESXi: the group logged in to ESXi hosts with vCenter's own service account and as root over SSH, added an SSH key for root, and copied Active Directory database and registry files out of a virtual machine's disk.
- Google's read: "BONESAW represents a significant expansion into post-compromise use of zero-days." Google notes BONESAW's build date predates this intrusion by more than a month, "indicating it was likely developed for broader operations".
Timeline
| Date | Event | Source |
|---|---|---|
| 13 Jul 2026 | Build timestamp in the BONESAW binary (Google notes this metadata can be altered) | |
| Early Sep 2026 | ARMORY CASTLE exploits CVE-2026-123890 with BONESAW, per forensic evidence | |
| 15 Oct 2026 | Google reports the group's BeyondTrust Remote Support zero-day; BeyondTrust advisory BT26-05 | Google, BeyondTrust |
| 16 Oct 2026 | CISA adds BeyondTrust CVE-2026-102764 to KEV | CISA KEV |
| 6 Nov 2026 | CVE-2026-123890 reserved by VMware | CVE record |
| 19 Nov 2026 | Broadcom publishes VMSA-2026-0009 with fixed vCenter builds; CVE published; Google and Mandiant publish their report | Broadcom, Google |
| 20 Nov 2026 | VMSA-2026-0009.1 clarifies affected VMware Tools versions. CVE-2026-123890 not in KEV (catalog 2026.11.18) | Broadcom |
What security leaders should do this week
- Patch every vCenter now to 9.1.1.0200, 9.0.2.0200, 8.0 U3m or VCF 5.2.5. There is no workaround. For vCenter 7.0, open a case with Broadcom if you have extended support; otherwise plan the upgrade and record the exception with an owner and a date in the risk register.
- Restrict who can reach vCenter. Management interfaces belong on an admin network reachable only from jump hosts. Google's hardening advice is a default-deny host firewall on the appliance with allow-lists for the management ports, including the directory service port 2012, plus egress filtering. Check from outside, not just from the config.
- Treat an unpatched vCenter that was reachable from user or server networks as possibly compromised. Hunt using Google's report and its published detections and indicators: unexpected SSO administrators, local accounts or machine accounts; unexpected Global Administrator grants; SSH being switched on through the appliance management API; Java processes spawning shells and unknown JSP files; new systemd services; server traffic to Slack. Forward appliance shell and firewall logs to your SIEM, since Google says the group deleted its tools and files.
- Check the ESXi hosts behind it for unexpected root SSH keys, root SSH and Host Client logins, and unfamiliar hidden directories on datastores. Rebuild a host you cannot vouch for.
- Rotate what vCenter holds, after patching. Google says the group stole the token-signing key, database credentials and the master encryption key. Our recommendation, following Broadcom's documented procedures: replace the vCenter token-signing (STS) certificate, reset SSO administrator and service-account passwords, and rotate the credentials vCenter uses for its database and ESXi hosts. If Active Directory files were copied from a VM disk, treat domain credentials as exposed and follow the leaked credential response steps.
- Close the way in. If you run BeyondTrust Remote Support self-hosted, confirm BT26-05 is installed (look it up in the KEV checker), and treat any remote-support or edge appliance as a path to your management plane. Rank the rest of the queue with the Vulnerability Prioritizer.
For the vendor record, see VMware (Broadcom) in the Breach Index. This is exploitation of a product flaw on a customer network, not a breach of Broadcom. To rehearse the decisions, try the Hypervisor Hardening Lab.
Frequently asked questions
What is CVE-2026-123890?
CVE-2026-123890 is an authentication bypass in the VMware Directory Service inside VMware vCenter. Broadcom rates it CVSS 3.1 9.8 Critical and says a network attacker with access to vCenter may bypass authentication and gain unauthorized access. It was fixed in VMware Security Advisory VMSA-2026-0009 on 19 November 2026.
Which vCenter versions fix CVE-2026-123890?
Per Broadcom VMSA-2026-0009: vCenter 9.1.1.0200 for 9.1.x, 9.0.2.0200 for 9.0.x, 8.0 U3m for 8.0, and VMware Cloud Foundation 5.2.5 for VCF 5.x. Telco Cloud Platform and Telco Cloud Infrastructure are covered by KB463116. vCenter 7.0 is affected; customers with an extended support contract must contact Broadcom Support. Broadcom lists no workaround.
Was the vCenter flaw exploited as a zero-day?
Yes, according to Google Threat Intelligence Group and Mandiant, who say forensic evidence shows ARMORY CASTLE exploited it in early September 2026, more than two months before the 19 November fix. Broadcom's advisory credits Mandiant with reporting the flaw but does not itself say whether it is exploited.
Who is ARMORY CASTLE?
Google calls ARMORY CASTLE a suspected PRC-nexus espionage actor, formerly tracked as UNC5221. The attribution is Google's and is worded as suspected. Google says the same group got its first foothold through a BeyondTrust Remote Support zero-day, CVE-2026-102764, before moving to vCenter.
What is BONESAW?
BONESAW is the name Google gives to a custom Go tool the group used to exploit CVE-2026-123890 against vCenter 7.x and 8.x. Google says it copied vCenter's directory database, extracted the key vCenter uses to sign login tokens, forged administrator tokens and created a new single sign-on (SSO) administrator account.
Is CVE-2026-123890 in CISA KEV?
Not as of 20 November 2026: the latest CISA Known Exploited Vulnerabilities catalog we checked (version 2026.11.18) does not list it. The BeyondTrust flaw used for initial access, CVE-2026-102764, has been in KEV since 16 October 2026.
Do I need to patch ESXi for CVE-2026-123890?
Broadcom's FAQ says ESX is not affected by VMSA-2026-0009, so the fix is a vCenter update. But Google says the attackers used what they took from vCenter to reach ESXi hosts, so an ESXi host managed by a compromised vCenter should be checked for unexpected root SSH keys and logins.
Was VMware or Broadcom breached?
No. Nothing reported shows a breach of Broadcom or VMware's own systems. This is a vulnerability in vCenter that was exploited on a customer's network; Google does not name the victim.
Sources
- Broadcom VMSA-2026-0009: VMware vCenter, Tools, and SDDC Manager updates address multiple vulnerabilities (19 November 2026, updated 20 November as VMSA-2026-0009.1)
- Broadcom: VMSA-2026-0009 questions and answers
- CVE.org: CVE-2026-123890 (CNA VMware, published 19 November 2026)
- Google Threat Intelligence Group and Mandiant: ARMORY CASTLE Exploits vSphere (19 November 2026)
- CISA KEV: CVE-2026-102764, BeyondTrust Remote Support, added 16 October 2026
- BeyondTrust security advisory BT26-05