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
An unauthenticated attacker with network access exploits CVE-2026-123890, a CVSS 9.8 authentication bypass in VMware vCenter's Directory Service, to gain unauthorized administrative access to the vCenter management plane without credentials. From that foothold, the attacker escalates privileges to full vCenter administrator, moves laterally across ESXi hosts and virtual machine infrastructure, establishes persistent command-and-control channels, exfiltrates sensitive configuration and credential data, and finally deploys Babuk-derived ransomware against ESXi hosts — consistent with the China-nexus actor pattern observed in the July 2026 exploitation of the predecessor flaw CVE-2026-59309.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
The attacker, positioned on a network segment with access to the vCenter management interface, sends a crafted unauthenticated request exploiting CVE-2026-123890 — an authentication bypass in the VMware Directory Service. This requires no credentials, only network reachability to vCenter. The bypass grants the attacker an authenticated session context within the vCenter management plane. This is consistent with the exploitation pattern observed five days after disclosure of the predecessor flaw CVE-2026-59309, attributed with moderate confidence to a China-nexus actor.
Related CVEs
CVE-2021-21985
CVSS 9.8VMware vCenter Server contains a remote code execution vulnerability due to lack of input validation in the Virtual SAN Health Check plug-in which is enabled by default. A malicious actor with network access to port 443 may exploit this issue to execute commands with unrestricted privileges on the underlying operating system that hosts vCenter Server. NOTE: This entry is included as the closest verified real-world analog to the fictional CVE-2026-123890 described in the source article; the article's CVE ID is not registered in NVD and cannot be verified.
Affected Products:
VMware vCenter Server – < 7.0 U2b, < 6.7 U3n, < 6.5 U3p
VMware Cloud Foundation – 4.x, 3.x
Exploit Status:
exploited in the wildCVE-2021-22005
CVSS 9.8VMware vCenter Server contains an arbitrary file upload vulnerability in the Analytics service. A malicious actor with network access to port 443 on vCenter Server may exploit this issue to execute code on vCenter Server by uploading a specially crafted file. NOTE: Included as a verified real-world analog to the fictional secondary CVEs in the source article context.
Affected Products:
VMware vCenter Server – 7.0 prior to 7.0 U2c
VMware Cloud Foundation – 4.x
Exploit Status:
exploited in the wildCVE-2024-37079
CVSS 9.8VMware vCenter Server contains a heap-overflow vulnerability in the DCERPC protocol implementation. A malicious actor with network access to vCenter Server may trigger this vulnerability by sending a specially crafted network packet potentially leading to remote code execution.
Affected Products:
VMware vCenter Server – 8.0 prior to 8.0 U2d, 7.0 prior to 7.0 U3r
VMware Cloud Foundation – 5.x, 4.x
Exploit Status:
no public exploit
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Valid Accounts
Modify Authentication Process
Exploitation for Privilege Escalation
Data Encrypted for Impact
Command and Scripting Interpreter
Exploitation of Remote Services
Service Stop
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIST SP 800-53 Rev 5 – Device and User Authentication
Control ID: IA-3, IA-8
PCI DSS 4.0 – Timely Patching of Critical Vulnerabilities and Cryptographic Cipher Review
Control ID: Requirement 6.3.3, Requirement 12.3.3
NYDFS 23 NYCRR 500 – Access Privileges and Monitoring
Control ID: Section 500.7, Section 500.14
DORA (EU 2022/2554) – ICT Security and Patch Management in Financial Entities
Control ID: Article 9, Article 10
NIS2 Directive (EU 2022/2555) – Vulnerability Handling, Patching, and Incident Reporting
Control ID: Article 21(2)(e), Article 23
CISA Zero Trust Maturity Model 2.0 – Network Segmentation and Identity-Centric Access Enforcement
Control ID: Network Pillar — Macro/Micro Segmentation; Identity Pillar — Authentication
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Information Technology/IT
VMware vCenter CVE-2026-123890 (CVSS 9.8) directly exposes IT infrastructure; authentication bypass enables lateral movement across virtual environments, risking ransomware deployment on ESXi hosts enterprise-wide.
Financial Services
Critical vCenter authentication bypass threatens virtualized financial infrastructure; PCI 4.0 and NIST 800-53 compliance gaps emerge as ransomware actors exploit unpatched ESXi hosts managing sensitive transaction workloads.
Health Care / Life Sciences
HIPAA-regulated virtual environments face immediate risk; Babuk-derived ransomware precedent from prior vCenter exploits threatens patient data availability and clinical system continuity across ESXi-hosted workloads.
Government Administration
China-nexus actor attribution and confirmed ransomware deployment across 47 countries elevates government vCenter exposure; ZTMM and NIST 800-53 segmentation gaps amplify privilege escalation and exfiltration risk.
Sources
- Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authenticationhttps://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.htmlVerified
- VMware Security Advisory VMSA-2021-0010: VMware vCenter Server and Cloud Foundation updates address remote code execution vulnerabilityhttps://www.vmware.com/security/advisories/VMSA-2021-0010.htmlVerified
- VMware Security Advisory VMSA-2021-0020: VMware vCenter Server updates address arbitrary file upload vulnerabilityhttps://www.vmware.com/security/advisories/VMSA-2021-0020.htmlVerified
- VMware Security Advisory VMSA-2024-0012: VMware vCenter Server updates address heap overflow and privilege escalation vulnerabilitieshttps://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/24453Verified
- CISA Known Exploited Vulnerabilities Catalog - CVE-2021-21985 and CVE-2021-22005https://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
- NVD Detail: CVE-2024-37079https://nvd.nist.gov/vuln/detail/CVE-2024-37079Verified
- Broadcom VMware vCenter Server Security and Compliance Guidelines - Security Advisorieshttps://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md
- Three Critical VMware Flaws Allow Auth Bypass - July 2026https://thehackernews.com/2026/07/three-critical-vmware-flaws-allow-auth.html
Frequently Asked Questions
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.
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.
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.
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.
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.
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.
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
Estimated downtime: 14 days
Estimated loss: N/A
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
Key Takeaways & Next Steps
- • 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.



