As reported by The Hacker News, Broadcom has disclosed a critical authentication bypass vulnerability in VMware vCenter Center (CVE-2026-123890) with a CVSS score of 9.8. The flaw resides in the VMware Directory Service (vmdir) and allows attackers with network access to bypass authentication entirely. Broadcom has released patches but explicitly states no workaround exists — and the advisory urges organizations to treat remediation as an emergency change under ITIL methodology.
This is not a routine patch cycle. vCenter is the administrative nerve center for entire virtualized estates — ESXi hosts, virtual machines, storage, networking, and increasingly, cloud workloads. An authentication bypass at the Directory Service layer means an attacker positioned anywhere on the reachable network could potentially assume administrative control of the entire virtualization stack without credentials. That is a domain-compromise-equivalent event for any organization whose infrastructure depends on vSphere.
Vulnerability Summary
| Field | Details |
|---|---|
| CVE ID | CVE-2026-123890 |
| CVSS Score | 9.8 (Critical) |
| Vulnerability Type | Authentication Bypass |
| Affected Component | VMware Directory Service (vmdir) |
| Affected Versions | vCenter 8.0, 9.0, 9.1; VMware Cloud Foundation (including 5.x); vSphere Foundation; Telco Cloud Platform & Infrastructure |
| Potentially Affected | vSphere 6.5, 6.7, 7.0 (out of general support, presumed vulnerable) |
| Patch Status | Patches available for supported branches |
| Workaround | None available |
| Active Exploitation | None reported at time of disclosure |
| Discoverer | Mandiant (Google) |
Why This Matters More Than a Typical CVE
Three factors elevate this beyond a standard critical patch. First, the absence of any workaround removes the breathing room organizations typically use to schedule maintenance windows. Second, vCenter's role as the central management plane means compromise cascades across every ESXi host and VM under its control — an attacker doesn't just breach one system, they gain a vantage point over the entire data center. Third, this is the second critical authentication flaw in vmdir this year, signaling a systemic weakness in the Directory Service component that threat actors and researchers are actively probing.
The fact that Mandiant — a firm typically engaged in incident response for sophisticated breaches — reported this vulnerability suggests it was discovered during real-world investigation, not a routine audit. That context matters for threat modeling.
Who Is Most Exposed
Patching Considerations
Broadcom notes the updates are cumulative and cannot be installed through vCenter Quick Patch. VMs continue running during the update, but management access drops temporarily, and Standard Key Provider encryption operations are unavailable until vCenter returns. There is also a critical upgrade path conflict: installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VMware Cloud Foundation 9.1.1. Organizations on VCF must either upgrade to vCenter 9.1.1 first and patch there, or wait for VCF 9.1.2.
Shield53 Recommendations
Immediate Actions
- Patch now. Treat this as an emergency change. Broadcom's advisory language is unambiguous — this qualifies under ITIL emergency change procedures. Do not wait for the next maintenance window.
- Isolate the vCenter management network. Until patched, restrict access to the vCenter network segment via firewall rules, VPN, and jump hosts. Reduce the attack surface to only essential administrative paths.
- Review vCenter access logs for anomalous authentication events, unusual source IPs, or administrative sessions from unexpected hosts — especially in the weeks preceding this disclosure, given Mandiant's involvement.
- Plan the upgrade path carefully if on VMware Cloud Foundation. The Back-in-Time conflict means a wrong patch sequence can strand you. Consult the VCF release notes before applying.
For Unsupported Versions (6.5 / 6.7 / 7.0)
- Network segmentation is your only mitigation. If you cannot patch, ensure vCenter has zero exposure to untrusted network paths. Assume the vulnerability is present.
- Accelerate migration plans to supported versions. Running vCenter on unsupported versions with known critical auth bypass flaws is an unacceptable risk posture.
- Request extended support patches for vSphere 7.0 if you have or can procure an extended support contract.
Longer-Term Hardening
- Audit vmdir exposure across all vCenter deployments and ensure the Directory Service is never reachable from general user networks
- Implement enhanced monitoring on vCenter authentication flows — given two critical vmdir flaws in one year, this component warrants persistent scrutiny
- Document and test emergency patching procedures for vCenter so future critical vulnerabilities can be remediated without operational surprises
The combination of critical severity, no workaround, central management plane exposure, and a second occurrence in the same component this year makes CVE-2026-123890 one of the highest-priority patches of 2026. Organizations that delay because of maintenance window politics are accepting domain-level risk for their virtualization infrastructure.