Executive Summary

On November 19, 2026, Broadcom disclosed CVE-2026-123890, a CVSS 9.8 authentication bypass in VMware vCenter's VMware Directory Service affecting vCenter 8.0, 9.0, and 9.1, as well as builds embedded in VMware Cloud Foundation, vSphere Foundation, and Telco Cloud Platform. Any attacker with network access to the vCenter management plane can bypass authentication entirely, gaining unauthorized control over virtualized infrastructure without credentials. No workaround exists; Broadcom classifies the fix as an emergency change under ITIL. Discovery was credited to Mandiant. No active exploitation has been confirmed at time of disclosure, though a parallel July 2026 vCenter bypass (CVE-2026-59309, also CVSS 9.8) was exploited within five days of disclosure, with a suspected China-nexus actor deploying Babuk-derived ransomware across 361 IP addresses in 47 countries.

This is the second critical authentication bypass in VMware Directory Service within four months. The pattern of near-immediate weaponization following prior vCenter disclosures, combined with the absence of a workaround and the breadth of affected product lines, makes rapid patching and network-level access controls around vCenter management interfaces operationally urgent for every virtualized enterprise environment.

Why This Matters Now

VMware vCenter is the administrative control plane for the majority of enterprise virtualization estates. A network-accessible authentication bypass with a CVSS of 9.8 and no workaround means any unpatched vCenter reachable from a compromised network segment is effectively owned. The July 2026 predecessor CVE was exploited within five days of disclosure; ransomware operators and China-nexus actors are already primed to weaponize this class of vulnerability, making immediate patching and strict east-west segmentation of management traffic non-negotiable.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

The flaw exposes failures in network access control and least-privilege segmentation. Organizations lacking zero trust segmentation around vCenter management interfaces violate NIST 800-53 SC-7 and AC-6, PCI DSS 4.0 requirement 7.2.4, and CISA ZTMM Network pillar controls, all of which mandate restricting administrative plane access to authorized, authenticated workloads only.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF is directly relevant to this incident because the attacker's entire kill chain depended on unrestricted network reachability to the vCenter management plane and an absence of east-west segmentation across the virtualized infrastructure. By enforcing identity-aware segmentation and controlled access paths, CNSF would likely reduce the attacker's ability to reach management interfaces, traverse the environment laterally, and establish undetected outbound channels.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: Network reachability to the vCenter management interface from unauthorized or untrusted segments would likely be constrained, reducing the pool of network positions from which an unauthenticated exploit attempt could realistically be launched.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust segmentation would likely constrain lateral reachability between the initial vCenter foothold and the SDDC Manager appliance, reducing the attacker's ability to chain vulnerabilities across adjacent management components without hitting an enforced policy boundary.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west enforcement would likely reduce the attacker's ability to move freely between ESXi hosts, management interfaces, and guest workloads, constraining how far a single compromised vCenter session could propagate across the virtualized environment.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Centralized multicloud visibility would likely surface anomalous outbound connection patterns from vCenter and ESXi management interfaces, reducing the attacker's ability to operate persistent C2 channels without generating observable traffic signals across the environment.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress security policy enforcement would likely constrain outbound data flows from the management network to only approved destinations, reducing the attacker's ability to exfiltrate extracted credentials and configuration data to unauthorized external infrastructure.

Impact (Mitigations)

If prior CNSF controls had reduced lateral reachability and constrained east-west traversal, the attacker's access to ESXi hosts at the time of ransomware deployment would likely have been scoped to fewer hosts — meaning the number of encrypted VM disk files and the breadth of workload disruption could have been materially smaller.

Impact at a Glance

Affected Business Functions

  • Virtual Infrastructure Management and Orchestration
  • ESXi Host and Virtual Machine Administration
  • Data Center Operations and Cloud Platform Services
  • Enterprise IT Security and Identity Access Controls
Operational Disruption

Estimated downtime: 14 days

Financial Impact

Estimated loss: N/A

Data Exposure

Exploitation of a CVSS 9.8 authentication bypass in VMware vCenter Directory Service could expose the entire virtual infrastructure management plane to unauthorized access. This includes administrative credentials stored in VMware Directory, virtual machine configurations and disk images, sensitive workload data hosted across ESXi hosts, and encryption key operations tied to Standard Key Providers. In environments where prior related traversal flaws (e.g., CVE-2026-59310 analog) were exploited, attackers deployed Babuk-derived ransomware against ESXi hosts across an estimated 361 IP addresses in 47 countries, suggesting risk of mass encryption of virtual machine storage, exfiltration of configuration and credential data, and prolonged operational outages across multi-tenant or enterprise data center environments. Organizations running end-of-life vSphere 6.5, 6.7, and 7.0 without patches face elevated risk of unmitigated compromise.

Recommended Actions

  • • Apply emergency patches for CVE-2026-123890 immediately across all affected vCenter 8.0, 9.0, and 9.1 deployments, including Cloud Foundation and Telco Cloud variants, as Broadcom provides no workaround and classifies this as an emergency change under ITIL methodology.
  • • Deploy Zero Trust Segmentation (microsegmentation) controls to enforce identity-based policy between vCenter management interfaces, ESXi hosts, and workloads — preventing unauthenticated or anomalous lateral movement across the east-west management plane even after initial compromise.
  • • Enable Multicloud Visibility and anomaly detection on vCenter management-plane traffic to detect repeated malformed authentication requests, anomalous API interactions, and suspicious automation patterns consistent with exploitation of authentication bypass CVEs before or during active attacks.
  • • Enforce Egress Security and Policy Enforcement with FQDN filtering on all outbound connections from vCenter and ESXi management networks to block unauthorized data exfiltration channels and C2 callbacks to attacker-controlled infrastructure following a management-plane compromise.
  • • Implement Inline IPS (Suricata-based) inspection on network paths leading to vCenter management interfaces to detect and block known exploit traffic signatures associated with CVE-2026-123890 and related VMware Directory Service bypass patterns, complementing but not replacing emergency patching.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image