Security Digest · Nov 19, 2026 · Vulnerability · Cloud
vCenter CVE-2026-123890: Auth Bypass Exploited as Zero-Day
A vCenter Directory Service flaw gives unauthenticated attackers SSO admin. China-linked hackers used it since September. Fixed in 8.0 U3m and 9.x builds.
Our verdict
Act now
Patch every vCenter now as an emergency change, including internal-only ones: a state-backed group used this flaw for months to become vSphere administrator from inside the network, and Broadcom lists no workaround.
Who must act: Every organization running vCenter Server 7.x, 8.x or 9.x, standalone or inside VMware Cloud Foundation, vSphere Foundation or Telco Cloud, whether or not vCenter faces the internet.
Who can relax: Teams with standalone ESX hosts and no vCenter, and VMware Workstation or Fusion users: Broadcom says ESX, Workstation and Fusion are not affected by this flaw.
- Affected
- vCenter 9.1.x before 9.1.1.0200
vCenter 9.0.x before 9.0.2.0200
vCenter 8.0 before 8.0 U3m
VMware Cloud Foundation 5.x before vCenter 8.0 U3m
vCenter 7.0 (end of general support; fixes only through extended support)
Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 and Telco Cloud Infrastructure 3.0 - Fixed in
- vCenter 9.1.1.0200
vCenter 9.0.2.0200
vCenter 8.0 U3m
VCF 5.x: vCenter 8.0 U3m via KB 88287, SDDC Manager 5.2.5 - CVSS
- 9.8 (v3.1, vendor)
- EPSS
- 3.0% (percentile 88)
- CISA KEV
- Yes, listed as known exploited
- Exploitation
- Exploited in the wild
- Severity
- Critical
What to do
- Inventory every vCenter, including lab, DR and Telco Cloud instances, and check each build in the vSphere Client Summary tab or with PowerCLI.
- Upgrade vCenter to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m today; VCF 5.x applies 8.0 U3m through the asynchronous patching process in KB 88287.
- Until patched, restrict vCenter ports 2012, 389, 636, 443, 5480 and 22 to admin jump hosts and peer vCenters at the network firewall.
- Review vsphere.local SSO users and the Administrators group for accounts nobody created.
- If you find signs of compromise, treat the SSO domain and its SAML signing key as stolen and bring in incident response before you rebuild trust.
- Also update SDDC Manager and VMware Tools for Windows, which VMSA-2026-0009 fixes in the same release.
How to check if you are affected or compromised
- Look for SSO administrator or machine accounts in vsphere.local that do not match a change ticket.
- Review firewall or flow logs for connections to vCenter TCP 2012 from hosts other than peer vCenters, and for internal nmap-style scans of ports 443, 2012, 389 and 5480.
- Check whether SSH or the bash shell was enabled on the vCenter appliance through the VAMI without an approved change.
- Run Mandiant's published YARA rules for BONESAW, SAWSNAKE, SLIMSAVAGE, CAGEMATCH, BEARBONES and LAZYBONES on Linux appliances near vCenter, especially ones without EDR.
What happened#
On November 19, 2026, Broadcom published VMSA-2026-0009, a critical advisory covering five flaws. The serious one is CVE-2026-123890, an authentication bypass in the VMware Directory Service (vmdir) inside vCenter Server, scored 9.8 under CVSS 3.1. Broadcom says an attacker with network access to vCenter can bypass authentication and gain unauthorized access. Its Q&A calls the patch an emergency change and lists no workaround.
The same day, Mandiant and Google Threat Intelligence Group reported that ARMORY CASTLE (formerly UNC5221), a suspected China-nexus espionage group, used the flaw as a zero-day in early September 2026. Mandiant explains the bug: vmdir's DCE/RPC interface for Secure Remote Password logins, on TCP port 2012, builds UUIDv1 values with predictable timestamps. That lets an attacker recover the session key without any password and open a session as administrator@vsphere.local.
The group's Go tool, BONESAW, used that session to create a Single Sign-On administrator account. It also copied the directory database (an LMDB file) and extracted the SAML token-signing key. A second tool, SAWSNAKE, forges SAML tokens with that key. From there the attackers reached ESX hosts and copied Active Directory database files out of virtual machines. The intrusion began with a BeyondTrust Remote Support zero-day, CVE-2026-102764, and moved through internal Linux appliances that had no EDR before it reached vCenter.
Who is affected#
vCenter 9.1.x before 9.1.1.0200, 9.0.x before 9.0.2.0200 and 8.0 before 8.0 U3m are affected, whether standalone or inside VMware Cloud Foundation, vSphere Foundation or Telco Cloud. Broadcom's Q&A says vSphere 7.0 is affected too. It reached end of general support on October 2, 2025, so patches come only through extended support contracts. Broadcom says to presume 6.5 and 6.7 are vulnerable. Enhanced Linked Mode makes no difference. ESX, NSX, Workstation and Fusion are not affected. Mandiant says BONESAW works against 7.x and 8.x appliances.
Do you really need to act?#
Yes, if you run vCenter. The flaw needs no credentials and no user interaction. A working exploit has been in a capable group's hands since at least September. Mandiant also says BONESAW was run against a server already patched for July's related flaw, CVE-2026-59309. Patching for that one gave no protection.
Keeping vCenter off the internet helps, but it did not save Mandiant's victim. The attackers entered through an edge appliance and attacked vCenter from inside the network. Treat "internal only" as a reason to patch in hours, not weeks. Update, November 21: CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities catalog on November 20, based on evidence of active exploitation. The KEV entry gives federal agencies until November 23, three days, and lists ransomware use as unknown. Broadcom had not confirmed exploitation itself when this brief was first published; Mandiant's forensic evidence was the original basis for listing it as exploited.
One planning note: Broadcom says vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1 until 9.1.2 ships. Teams in the middle of that upgrade should still patch now and wait briefly for 9.1.2.
What to do now#
- Find every vCenter you run, including lab and DR instances. Check the build in the vSphere Client Summary tab, or with PowerCLI:
Connect-VIServer, then$global:DefaultVIServer.Versionand$global:DefaultVIServer.Build. - Upgrade to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m through the VAMI or your normal update process. Workloads keep running while vCenter restarts. VCF 5.x customers apply 8.0 U3m through KB 88287 and update SDDC Manager to 5.2.5.
- Until you patch, allow vCenter ports 2012, 389, 636, 443, 5480 and 22 only from admin jump hosts and peer vCenters. Mandiant's VCSA hardening tool applies default-deny iptables rules and egress filtering on the appliance. Test it before using it in production.
- Update SDDC Manager and VMware Tools for Windows, which the same advisory fixes (CVE-2026-123891 to CVE-2026-123894).
- If you find signs of intrusion, assume the SAML signing key was stolen. Patching does not invalidate tokens forged with a stolen key, so bring in incident response before you rebuild trust.
How to tell if you were hit#
In the vSphere Client, open Administration, Single Sign On, Users and Groups. Compare the members of the vsphere.local Administrators group against your records, and look for new solution or machine accounts. Search flow and firewall logs for connections to TCP 2012 on vCenter from anything other than peer vCenters, and for internal scans of ports 443, 2012, 389 and 5480. Check whether SSH was enabled on the appliance without a change ticket. Mandiant published YARA rules for BONESAW, SAWSNAKE and the SLIMSAVAGE, CAGEMATCH, BEARBONES and LAZYBONES implants. Its network and file indicators are in a Google Threat Intelligence collection for registered users. A clean result is weak evidence if the attacker had the signing key, because forged tokens look like normal administrator logins.
Timeline#
- — Broadcom discloses CVE-2026-59309, a separate vmdir authentication bypass. Mandiant says ARMORY CASTLE already knew about CVE-2026-123890.
- — ARMORY CASTLE exploits CVE-2026-123890 against a victim's internal vCenter in early September, according to Mandiant.
- — Mandiant and GTIG report the same group's BeyondTrust Remote Support zero-day.
- — Broadcom publishes VMSA-2026-0009 with fixed vCenter builds, and Mandiant publishes its analysis of the vSphere intrusion.
- — CISA adds CVE-2026-123890 to KEV with a November 23 due date.
Vulnerability records
- CVE-2026-123890 · KEV 2026-11-20 · VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service.
Sources
Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.
Original and primary sources
- Broadcom — VMware Security Advisory VMSA-2026-0009 support.broadcom.com
- Broadcom — VMSA-2026-0009 Questions & Answers github.com
- CVE record — CVE-2026-123890 cve.org
- Mandiant and Google Threat Intelligence Group — ARMORY CASTLE Exploits vSphere cloud.google.com
- Mandiant — VCSA Hardening & Logging Tool github.com
- CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog (Nov 20, 2026) cisa.gov
- CISA — Known Exploited Vulnerabilities catalog entry for CVE-2026-123890 cisa.gov