CVE-2026-123890 - VMWare vCenter Authentication Bypass Using an Alternate Path or Channel Vulnerability

CVE-2026-123890

VMware vCenter - Pre-Auth Administrator Takeover via VMware Directory Service

What is VMware vCenter?

VMware vCenter Server is the central management plane for a vSphere estate. It inventories ESX hosts, schedules and migrates virtual machines, holds the credentials and encryption keys used for VM encryption, and provides the single sign-on (SSO) identity service that every administrator authenticates against. The identity half of that job runs in the VMware Directory Service, which stores principals, groups and SAML signing material in an embedded LMDB database.

That makes vCenter one of the highest-value targets in an enterprise network. Administrator access to vCenter is effectively administrator access to every workload it manages: an attacker can clone or snapshot virtual machines, read guest disks, push commands to ESX hosts, and mint SSO sessions that look legitimate to everything downstream. Most organizations place vCenter on an internal management network rather than the internet, which means an exploit like this one usually gets used after an intrusion has already started, as the step that converts a foothold into control of the virtual estate.

Overview

CVE-2026-123890 is an authentication bypass in the VMware Directory Service component of vCenter Server. An unauthenticated attacker with network access to the vCenter appliance can reach an alternate authentication path and come away with an authenticated session as the Administrator user. There is no user interaction, no credential requirement and no need for Enhanced Linked Mode; Broadcom scored it 9.8 under CVSS 3.1 with the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Broadcom disclosed the flaw on 2026-11-19 in advisory VMSA-2026-0009, which bundles five issues. The other four are lower rated (6.7 to 8.1) and affect SDDC Manager (CVE-2026-123891 SQL injection, CVE-2026-123892 command injection, CVE-2026-123893 root privilege escalation) and VMware Tools for Windows (CVE-2026-123894, a SAML token signature bypass that applies only where Guest Alias mapping is configured). Broadcom's FAQ states that none of the five allows code execution on an ESX host from inside a guest VM.

It had already been exploited for more than two months by the time the patch shipped. Mandiant, which reported the bug to Broadcom, observed a suspected China-nexus espionage actor using it from early September 2026. Broadcom's own advisory does not mention in-the-wild exploitation; CISA added the CVE to the KEV catalog on 2026-11-20 with a three-day remediation deadline. This is a distinct bug from CVE-2026-59309, the VMware Directory Service bypass disclosed on 2026-07-29, and the earlier patch does not block it.

Affected Versions

Product Vulnerable Fixed
VCF / vSphere Foundation (vCenter) 9.1.x.x 9.1.1.0200
VCF / vSphere Foundation (vCenter) 9.0.x.x 9.0.2.0200
vCenter Server 8.0 8.0 U3m
vCenter Server 7.0 No public patch; extended-support customers contact Broadcom
VMware Cloud Foundation 5.x 5.2.5
Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 vCenter 8.0 U3m per KB 463116
Telco Cloud Infrastructure 3.0 vCenter 8.0 U3m per KB 463116

vSphere 6.5 and 6.7 are past end of support and are not evaluated by Broadcom; treat them as vulnerable. ESX itself is not affected. Note the upgrade ordering trap: 8.0 U3m and 9.0.2.0200 block a later upgrade to VCF 9.1.1, so sites heading to 9.1 should move to 9.1.1 first and patch there, or wait for VCF 9.1.2.

Technical Details

CISA and Rapid7 classify the flaw as CWE-288, authentication bypass using an alternate path or channel. In plain terms, the Directory Service exposes more than one way to establish an authenticated session, and one of those paths does not enforce the checks the main login path does. An attacker who speaks to that path directly is treated as an already-authenticated principal rather than being asked to prove anything.

Attack characteristics are about as bad as they get: network reachable, low complexity, no privileges, no user interaction, and the resulting session carries Administrator rights. Neither Broadcom nor Google has published the vulnerable code path or a proof of concept, and public reporting does not pin the bug to a named function. Broadcom lists no workaround, and the fixes are cumulative and cannot be applied through vCenter Quick Patch, so remediation means a full update with a short management-plane outage. Running VMs keep running during it, though encryption operations against a Standard Key Provider are unavailable until vCenter returns.

Discovery

Mandiant, now part of Google Cloud, found the vulnerability while investigating intrusions and reported it privately to Broadcom. Google Threat Intelligence Group published its own analysis on 2026-11-20, a day after the advisory. Mandiant CTO Charles Carmakal stated publicly that Mandiant worked multiple incidents involving exploitation of this CVE and urged organizations to patch and then hunt for evidence of compromise rather than assume the patch is sufficient.

Exploitation Context

Google attributes the exploitation to ARMORY CASTLE, a suspected China-nexus espionage actor formerly tracked as UNC5221 and also reported under the name Warp Panda. In the intrusions Mandiant investigated, initial access came from a separate flaw, CVE-2026-102764 in BeyondTrust Remote Support; the actor then pivoted to internal Linux appliances and attacked vCenter in early September 2026.

On the appliance the actor ran a Go-based exploitation utility that Google tracks as BONESAW, which targets vCenter 7.x and 8.x. Reporting describes it copying the Directory Service LMDB database, extracting SAML signing material, and creating a single sign-on administrator account. A second tool, SAWSNAKE, was staged on the appliance to forge SAML assertions and generate session cookies, a Golden SAML capability that yields administrator sessions without multi-factor authentication. The actor also took the vCenter master encryption key and database credentials, then moved on to an ESX host. Published file-path indicators include /tmp/123 for BONESAW and /tmp/sss for SAWSNAKE, alongside tooling tracked as BEARBONES and LAZYBONES. One recovered BONESAW sample carries a 2026-07-13 build timestamp, which is consistent with Google's assessment that the actor knew of this bug before the July CVE-2026-59309 disclosure, but build timestamps can be forged.

Notably, the targeted vCenter had already been patched for CVE-2026-59309. No public internet-exposure count has been published for this CVE, which is unsurprising given that vCenter is usually internal; the relevant exposure is to anything already inside the management network.

Remediation

  1. Update vCenter to a fixed build now: 9.1.1.0200, 9.0.2.0200 or 8.0 U3m, or the corresponding VCF 5.2.5 or Telco Cloud build per KB 463116. Broadcom classifies this as an emergency change. The federal BOD 26-04 deadline is 2026-11-23.
  2. If you are on vCenter 7.0 and hold extended support, contact Broadcom for a patch. If you do not, treat the appliance as unfixable and isolate it while you plan an upgrade.
  3. If you intend to move to VCF 9.1.1, upgrade first and apply the fix there, to avoid the Back-in-Time restriction that 8.0 U3m and 9.0.2.0200 impose.
  4. There is no vendor workaround. Until patched, restrict network access to the vCenter appliance and its SSO endpoints to a small set of management jump hosts, and make sure vCenter is not reachable from user VLANs, VPN pools or the internet.
  5. Hunt for compromise rather than assuming the patch closed the door. Look for unexpected SSO administrator accounts, administrator sessions that bypassed MFA, unfamiliar processes or files under /tmp on the appliance (including /tmp/123 and /tmp/sss), access to the Directory Service LMDB files, and outbound connections from the vCenter appliance. Apply the same scrutiny to ESX hosts the appliance manages.
  6. If you find evidence of access, rotate the vCenter master encryption key, SSO credentials, SAML signing certificates and vCenter database credentials, since the published tradecraft steals all of them. Rotating after patching does nothing if the patch came first and the keys stayed.
  7. Review the other four VMSA-2026-0009 issues in the same maintenance window, particularly the SDDC Manager command injection and root escalation bugs.

Key Details

PropertyValue
CVE ID CVE-2026-123890
Vendor / Product Broadcom - VMware vCenter
NVD Published2026-11-19
NVD Last Modified2026-11-20
CVSS 3.1 Score9.8
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
SeverityCRITICAL
CWE CWE-288 find similar ↗
CISA KEV Added2026-11-20
CISA KEV Deadline2026-11-23
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Required Action

CISA BOD 26-04 Deadline: 2026-11-23. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA's "Forensics Triage Requirements" (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines

Timeline

DateEvent
2026-07-29Broadcom discloses CVE-2026-59309, a separate VMware Directory Service authentication bypass; Google later assesses that the actor already knew of CVE-2026-123890 by this date
2026-09-01Earliest observed in-the-wild exploitation; Mandiant dates the activity to early September 2026
2026-11-19Broadcom publishes VMSA-2026-0009 and patched builds; CVE record published
2026-11-20Google Threat Intelligence publishes its ARMORY CASTLE analysis
2026-11-20Added to CISA Known Exploited Vulnerabilities catalog
2026-11-23CISA BOD 26-04 remediation deadline