Vulnerability
CVE-2026-123890: VMware vCenter Authentication Bypass (CVSS 9.8) Exploited as Zero-Day and Added to CISA KEV
Broadcom released VMSA-2026-0009 on November 19, 2026, patching CVE-2026-123890 (CVSS 3.1 9.8), a critical authentication bypass in VMware vCenter Server's Directory Service (vmdir). Google Threat Intelligence Group and Mandiant reported that suspected PRC-nexus actor ARMORY CASTLE (formerly UNC5221) exploited the flaw as a zero-day since early September 2026 using custom tooling including BONESAW and SAWSNAKE. CISA added CVE-2026-123890 to the Known Exploited Vulnerabilities (KEV) Catalog on November 20, 2026, with a federal remediation deadline of November 23, 2026. No workaround exists.
11 min read
CVE-2026-123890: VMware vCenter Authentication Bypass (CVSS 9.8) Exploited as Zero-Day and Added to CISA KEV
Executive Summary
On November 19, 2026, Broadcom published VMware Security Advisory VMSA-2026-0009 (updated November 20 as VMSA-2026-0009.1) to address CVE-2026-123890, a critical authentication bypass vulnerability in the VMware Directory Service (vmdir) component of VMware vCenter Server. Assigned a CVSS v3.1 base score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and classified under CWE-288 (Authentication Bypass Using an Alternate Path or Channel) in the CVE.org record, the flaw allows an unauthenticated attacker with network access to vCenter to bypass authentication and gain unauthorized administrative access.
On the same day Broadcom released patches, Google Threat Intelligence Group (GTIG) and Mandiant disclosed that a suspected PRC-nexus espionage group tracked as ARMORY CASTLE (formerly UNC5221) had exploited CVE-2026-123890 as a zero-day since early September 2026—more than two months prior to patch availability. On November 20, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-123890 to its Known Exploited Vulnerabilities (KEV) Catalog, establishing a federal civilian agency remediation deadline of November 23, 2026 under Binding Operational Directive (BOD) 26-04 (Senserva).
Broadcom lists no workaround for CVE-2026-123890 and notes that the updates cannot be delivered via vCenter Quick Patch (Rapid7). Because vCenter serves as the centralized management plane for virtualized infrastructure, organizations must treat patching as an emergency change and pair remediation with forensic hunting for signs of prior compromise.
| Attribute | Verified Detail |
|---|---|
| CVE Identifier | CVE-2026-123890 (CVE.org) |
| CVSS v3.1 Score | 9.8 Critical (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) |
| Weakness Type | CWE-288 (Authentication Bypass Using an Alternate Path or Channel) |
| Affected Component | VMware Directory Service (vmdir) in VMware vCenter Server |
| Exploitation Status | Exploited in the wild since early September 2026 (GTIG / Mandiant) |
| Attributed Threat Actor | ARMORY CASTLE (formerly UNC5221), suspected PRC-nexus espionage actor |
| CISA KEV Status | Added November 20, 2026; federal due date November 23, 2026 |
| Vendor Advisory | VMSA-2026-0009.1 (Issued Nov 19, 2026; updated Nov 20, 2026) |
| Workarounds | None |
Affected Versions and Exposure Scope
Broadcom's response matrix in VMSA-2026-0009.1 confirms that CVE-2026-123890 affects multiple branches of standalone VMware vCenter Server, VMware Cloud Foundation (VCF), VMware vSphere Foundation, and VMware Telco Cloud deployments across any running platform, with no special configuration required for exposure.
| Product / Deployment Line | Affected Versions | Fixed Version / Remediation Path | Notes |
|---|---|---|---|
| VMware Cloud Foundation / vSphere Foundation (vCenter) | 9.1.x.x (prior to 9.1.1.0200) |
9.1.1.0200 |
Cumulative update; no workaround |
| VMware Cloud Foundation / vSphere Foundation (vCenter) | 9.0.x.x (prior to 9.0.2.0200) |
9.0.2.0200 |
Triggers "Back-in-Time" block to VCF 9.1.1 |
| VMware vCenter Server | 8.0 (prior to 8.0 U3m) |
8.0 U3m |
Triggers "Back-in-Time" block to VCF 9.1.1 |
| VMware vCenter Server | 7.0 (All) |
Contact Broadcom Support | Extended-support contract required; no public patch |
| VMware Cloud Foundation (vCenter) | 5.x (prior to 5.2.5) |
5.2.5 (vCenter 8.0 U3m + SDDC Manager 5.2.5) |
Apply via Async Patching Guide (KB88287) |
| VMware Telco Cloud Platform | 3.0, 4.x, 5.0.x, 5.1.x, 5.2 |
8.0 U3m via KB463116 |
Follow Broadcom KB463116 |
| VMware Telco Cloud Infrastructure | 3.0 |
8.0 U3m via KB463116 |
Follow Broadcom KB463116 |
Scope Caveats and Upgrade Constraints
Administrators planning emergency rollouts should account for five operational constraints documented in Broadcom's advisory and supplemental guidance summarized by SOCRadar and PlayCISO:
- No vCenter Quick Patch Support: vCenter Quick Patch cannot deliver the cumulative updates required to resolve CVE-2026-123890. Standard appliance update procedures must be used. Updating vCenter temporarily interrupts management interfaces, though Broadcom states that running virtual machine and container workloads continue operating during the update (Rapid7).
- Enhanced Linked Mode Independence: The vulnerability resides in vCenter Server itself and applies regardless of whether Enhanced Linked Mode (ELM) is configured.
- End-of-Support and vSphere 7.0 Exposure: vSphere 7.0 reached end of general support on October 2, 2025, and has no public patch for CVE-2026-123890; only customers with an extended support contract can obtain a fix from Broadcom Support. Broadcom does not assess end-of-support releases and advises treating vSphere 6.5 and 6.7 as vulnerable. Because GTIG observed that ARMORY CASTLE's exploitation tooling operates against both vCenter 7.x and 8.x, unpatched 7.x deployments remain at acute risk (SOCRadar).
- "Back-in-Time" VCF Upgrade Restriction: Applying vCenter
8.0 U3mor9.0.2.0200introduces a "Back-in-Time" restriction that blocks subsequent upgrades to VMware Cloud Foundation9.1.1. Broadcom advises organizations currently in an active upgrade path to VCF 9.1.1 to review the vendor FAQ and interoperability matrix or wait briefly for VCF9.1.2while enforcing strict management-plane isolation (Rapid7, SOCRadar). - ESXi Hosts Not Directly Vulnerable: Broadcom's FAQ clarifies that ESXi hypervisors are not directly affected by CVE-2026-123890 and do not receive a patch under VMSA-2026-0009. However, because vCenter holds administrative control over managed ESXi hosts, compromising vCenter provides attackers a direct pivot into the underlying hypervisor layer.
Additional Vulnerabilities in VMSA-2026-0009.1
While CVE-2026-123890 is the only flaw in the advisory with confirmed in-the-wild exploitation, VMSA-2026-0009.1 also patches four additional vulnerabilities across SDDC Manager and VMware Tools for Windows:
- CVE-2026-123891 (CVSS 8.1, Important): Authenticated SQL injection in SDDC Manager (
5.2.5,9.0.2.0100,9.1.1.0200), allowing unauthorized database read/write operations. - CVE-2026-123892 (CVSS 7.2, Important): Authenticated command injection in SDDC Manager (
5.2.5,9.0.2.0100,9.1.1.0200), enabling arbitrary command execution on the appliance. - CVE-2026-123893 (CVSS 6.7, Moderate): Local privilege escalation in SDDC Manager and VCF Installer (
5.2.5,9.0.2.0100,9.1.1.0200), allowing an authenticated administrator to elevate to root. - CVE-2026-123894 (CVSS 6.7, Moderate): SAML token signature bypass in VMware Tools for Windows (
13.1.5.0,12.5.5, and12.4.10for 32-bit Windows), affecting guest VMs configured with Guest Alias mapping.
Root Cause and Attack Vector Analysis
Mechanism of the vmdir Authentication Bypass
The VMware Directory Service (vmdir) backs vCenter Single Sign-On (SSO), storing the directory database (data.mdb), identity records, and credentials trusted across the vSphere management plane (SOCRadar). According to technical findings published by GTIG and Mandiant and summarized by Brandefense and SOCRadar, CVE-2026-123890 stems from an unauthenticated disclosure of a Secure Remote Password (SRP) session key through vmdir's remote procedure call (RPC) interface listening on TCP port 2012.
By obtaining that SRP session key without supplying a password, a remote actor with network reachability to TCP port 2012 can establish an authenticated administrative session as the built-in Administrator@vsphere.local account. Broadcom has not publicly disclosed the exact vulnerable function or packet sequence, and no public exploit code has been reported as of November 20, 2026 (SOCRadar).
Distinction from CVE-2026-59309
CVE-2026-123890 is the second critical vmdir authentication bypass Broadcom has patched in 2026, following CVE-2026-59309, which was addressed on July 29, 2026 (PlayCISO). Broadcom's FAQ explicitly states that CVE-2026-123890 is a "new and distinct issue," meaning environments patched against CVE-2026-59309 remain vulnerable until updated to the VMSA-2026-0009 builds (Help Net Security). Notably, Mandiant reported that the recovered exploitation tool succeeded against a vCenter instance already patched for CVE-2026-59309, and forensic metadata—specifically a July 13, 2026 build timestamp in the compiled Go binary, though subject to tampering—suggests ARMORY CASTLE may have been aware of the flaw prior to the July disclosure (SOCRadar, PlayCISO).
Observed ARMORY CASTLE Intrusion Chain
GTIG and Mandiant reconstructed an end-to-end intrusion from early September 2026 illustrating how ARMORY CASTLE combined edge-appliance zero-days with post-compromise virtualization targeting:
[External Edge]
BeyondTrust Remote Support (CVE-2026-102764 zero-day, late Aug 2026)
│
▼
[Internal Pivot]
Internal Linux Appliance (no EDR) ──► SLIMSAVAGE web shells + internal scan (ports 443, 5480, 2012)
│
▼
[vCenter Takeover via CVE-2026-123890]
vmdir RPC (TCP 2012) ──► BONESAW (Go tool) leaks SRP session key ──► Dumps data.mdb & creates SSO admin
│
├──► SAWSNAKE mints forged Golden SAML tokens (bypasses MFA)
├──► Appliance API toggles SSH ON ──► Steals master key & PostgreSQL creds ──► SSH toggled OFF
│
▼
[Hypervisor & Workload Impact]
ESXi Hosts (root/vpxuser SSH, BEARBONES, LAZYBONES) ──► Copies Active Directory DB from guest VM disks
Key stages documented by GTIG/Mandiant, SOCRadar, and PlayCISO include:
- Initial Perimeter Access: The actor first breached the target network in late August 2026 via CVE-2026-102764, a BeyondTrust Remote Support zero-day fixed in advisory BT26-05 on October 15 and added to CISA KEV on October 16, 2026.
- Internal Appliance Foothold: From BeyondTrust, the operators pivoted to an internal Linux appliance lacking endpoint detection and response (EDR) telemetry, deployed SLIMSAVAGE web shells, escalated to root, and scanned internal subnets for VMware management ports (
443,5480, and2012). - vCenter Exploitation via BONESAW: Using a custom Go utility named BONESAW (compatible with vCenter 7.x and 8.x), the attackers exploited CVE-2026-123890 over port 2012 to extract a copy of
data.mdb, create a backdoor machine account, grant Global Administrator privileges, and establish a persistent SSO administrator account. - Golden SAML Forgery and Secret Extraction: Using SAML signing material extracted from the directory database, a second Go tool (SAWSNAKE) minted forged SAML tokens ("Golden SAML") to impersonate users and bypass multi-factor authentication (MFA). The operators also temporarily enabled SSH via the vCenter Appliance Management Interface (VAMI), harvested the vCenter master encryption key and PostgreSQL credentials, and disabled SSH afterward to minimize log trails.
- Hypervisor and Active Directory Reach: With vCenter compromised, ARMORY CASTLE authenticated to underlying ESXi hosts using vCenter's
vpxuserservice account androotSSH, added unauthorized SSH keys, and extracted Active Directory database (ntds.dit) and registry files directly from guest domain controller VM disks. Alongside BONESAW and SAWSNAKE, responders identified BEARBONES (a trojanized Dropbear SSH server logging credentials), CAGEMATCH (a JSP web shell), and LAZYBONES (a backdoor using Slack for command and control).
Detection, Threat Hunting, and Mitigation
Because ARMORY CASTLE actively removes tools such as SAWSNAKE after execution and exploits gaps on unmonitored Linux appliances, patching alone is insufficient if a vCenter instance was reachable from internal server or remote-support subnets prior to November 19, 2026 (PlayCISO).
1. Emergency Patching and Management-Plane Isolation
- Apply VMSA-2026-0009.1 Immediately: Upgrade vCenter deployments to
9.1.1.0200,9.0.2.0200,8.0 U3m, or VCF5.2.5(KB88287) outside normal maintenance windows, and apply Telco Cloud updates per KB463116. Federal Civilian Executive Branch (FCEB) agencies must complete remediation by November 23, 2026 per CISA BOD 26-04 (Senserva). - Enforce Default-Deny Host Firewalls: Restrict inbound access to vCenter TCP ports
443,2012(vmdir),5480(VAMI), and22(SSH) strictly to dedicated administrative jump hosts. Audit firewall logs to verify that remote-support appliances (such as BeyondTrust) and general server VLANs cannot reach port2012. - Verify Patch Compliance: After deployment, query the running appliance build version directly and cross-check it against Broadcom's Response Matrix.
2. Threat Hunting Indicators (Post-Compromise Triage)
Defenders should inspect centralized SIEM logs, vCenter appliances, and managed ESXi hosts for indicators documented from GTIG and Mandiant's investigation (SOCRadar, PlayCISO):
- vCenter SSO and Directory Anomalies: Audit
vsphere.localfor unauthorized administrator or machine accounts and unexpected Global Administrator role assignments; in the investigated intrusion, the actor created an SSO account prefixed withsps-. - SSH Toggling via VAMI: Inspect appliance management API logs for
PUTrequests to/rest/appliance/access/sshtoggling SSH on and off outside approved change tickets. - Suspicious Appliance Artifacts: Check vCenter filesystems for unexpected JSP web shells (
ActiveSer.jsp,u.jsp), staging paths (/tmp/123,/tmp/sss,/tmp/dbr,/tmp/123.key),/usr/bin/vmtoolscs, unauthorizedsystemdservices, or Java processes spawning shell commands. - ESXi Host Indicators: Inspect
/etc/ssh/keys-root/authorized_keyson ESXi hosts for added SSH keys, check datastores for a hidden.adirectory orvmfs-pydist.tar.gz, and reviewrootandvpxuserlogins from anomalous source IPs. - Network and C2 Signatures: Flag internal SSH services advertising the banner
SSH-2.0-pulsesecure_23345on high ports, as well as unexpected outbound HTTPS traffic from vCenter or internal Linux appliances to Slack APIs (associated with LAZYBONES). - Upstream BeyondTrust Check: If self-hosted BeyondTrust Remote Support is deployed, confirm advisory
BT26-05(CVE-2026-102764) is patched and audit any internal Linux appliances reachable from it (PlayCISO).
3. Post-Compromise Credential and Key Rotation
If hunting uncovers evidence of unauthorized access—or if an unpatched vCenter instance was exposed to untrusted internal or external networks—patching closes the initial vector but does not invalidate stolen cryptographic material. Following Broadcom's documented procedures, affected teams should (SOCRadar, PlayCISO):
- Rotate the vCenter Security Token Service (STS) / SAML signing certificate to invalidate any forged Golden SAML tokens.
- Rotate the vCenter master encryption key and PostgreSQL database credentials.
- Reset all SSO administrator and vCenter-to-ESXi service account (
vpxuser) passwords. - Treat Active Directory domain credentials as compromised if any evidence suggests guest domain controller VM disks were accessed or copied from ESXi datastores.
Frequently Asked Questions
Does CVE-2026-123890 require valid credentials or user interaction?
No. Broadcom and the CVE.org record confirm a CVSS v3.1 vector of AV:N/AC:L/PR:N/UI:N, meaning an unauthenticated attacker with network access to vCenter's vmdir RPC port (2012) can exploit the flaw with zero privileges and no user interaction.
Which VMware vCenter versions fix CVE-2026-123890?
Per VMSA-2026-0009.1, fixed builds are 9.1.1.0200 (for 9.1.x), 9.0.2.0200 (for 9.0.x), 8.0 U3m (for standalone 8.0), and VCF 5.2.5 (using vCenter 8.0 U3m via KB88287 and SDDC Manager 5.2.5). Telco Cloud Platform and Infrastructure deployments are remediated via KB463116.
Is there a workaround or Quick Patch for CVE-2026-123890?
No. Broadcom explicitly lists "None" for workarounds and confirms vCenter Quick Patch cannot deliver these updates (Rapid7). Firewalling TCP port 2012 and management interfaces to dedicated admin hosts reduces exposure but does not replace patching.
Is CVE-2026-123890 in the CISA KEV Catalog?
Yes. CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities (KEV) Catalog on November 20, 2026, with a federal remediation deadline of November 23, 2026 (Senserva).
Are VMware ESXi hosts directly vulnerable to CVE-2026-123890?
No. Broadcom's FAQ confirms ESXi is not directly affected by VMSA-2026-0009. However, because GTIG observed attackers pivoting from a compromised vCenter into managed ESXi hosts, administrators must still audit ESXi authorized_keys, datastores, and root/vpxuser logins if vCenter was exposed.
Sources
- Broadcom Support Portal — VMSA-2026-0009.1: VMware vCenter, Tools, and SDDC Manager updates address multiple vulnerabilities (Published Nov 19, 2026; Updated Nov 20, 2026): https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
- Broadcom Knowledge Base — VMware Telco Cloud response to VMSA-2026-0009 (KB463116) (Nov 20, 2026): https://knowledge.broadcom.com/external/article/463116
- CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog (Nov 20, 2026): https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog
- CVE Program (CVE.org) — CVE-2026-123890 Record (CNA: VMware by Broadcom) (Nov 19, 2026): https://www.cve.org/CVERecord?id=CVE-2026-123890
- Rapid7 Emergent Threat Response — CVE-2026-123890: Critical Authentication Bypass in VMware vCenter (Nov 19, 2026): https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter/
- SOCRadar — CVE-2026-123890: vCenter Zero-Day Exploited by Armory Castle (Nov 20, 2026): https://socradar.io/blog/cve-2026-123890-vcenter-0day-armory-castle/
- Brandefense — VMware vCenter Authentication Bypass (CVE-2026-123890) (Nov 19, 2026): https://brandefense.io/knowledge-hub/vulnerabilities/cve-2026-123890/
- PlayCISO — VMware vCenter CVE-2026-123890 Zero-Day: What to Do (Nov 20, 2026): https://playciso.com/blog/vmware-vcenter-cve-2026-123890-armory-castle
- Help Net Security — VMware vCenter zero-day exploited for months before patch (CVE-2026-123890) (Nov 20, 2026): https://www.helpnetsecurity.com/2026/11/20/vmware-vcenter-zero-day-cve-2026-123890-exploited/
- Senserva — CVE-2026-123890 KEV Remediation Due Date Tracking (Nov 21, 2026): https://senserva.com/cve/CVE-2026-123890.html