Critical VMware vCenter Flaw Lets Network Attackers Skip Login, and There Is No Workaround
Broadcom, which owns VMware, has published an advisory for a critical flaw in VMware vCenter that lets an attacker with network access bypass authentication and gain unauthorized access. The bug is tracked as CVE-2026-123890 and rated 9.8 on the CVSS scale. It sits in the VMware Directory Service. vCenter is the central console used to manage ESX hosts and virtual machines. Mandiant reported the flaw.
Fixed versions are available for all supported branches, but Broadcom lists no workaround. Affected products include vCenter 8.0, 9.0 and 9.1, plus the vCenter builds inside VMware Cloud Foundation (including the older 5.x line), vSphere Foundation, and the Telco Cloud Platform and Infrastructure. Enhanced Linked Mode makes no difference. Broadcom no longer evaluates versions past end of support, so vSphere 6.5 and 6.7 should be presumed affected, as should vSphere 7.0, which left general support in October 2025. Extended support customers can request a patch. Broadcom calls the fix an emergency change and has not said what access an attacker gets after the bypass.
The updates are cumulative and cannot be installed through vCenter Quick Patch. Virtual machines keep running during the update, though management access drops briefly and some encryption operations against a Standard Key Provider are unavailable until vCenter returns. Installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VMware Cloud Foundation 9.1.1. Affected teams can upgrade vCenter to 9.1.1 first and apply the security update there, or wait briefly for VCF 9.1.2.
This is the second critical Directory Service authentication flaw this year. In July, Broadcom patched CVE-2026-59309 and a directory-traversal bug, CVE-2026-59310. QUIRSO assessed that attacks on the traversal flaw began five days after disclosure and compromised an estimated 361 IP addresses in 47 countries, deploying Babuk-derived ransomware on ESXi hosts. No attacks on the new bypass have been reported.
Why it matters
Any organisation running vCenter, including those on unsupported 6.5, 6.7 or 7.0 builds, cannot rely on a configuration change to reduce risk, so patching or restricting network reach is the only decision on the table. The earlier Directory Service flaws were exploited within days of disclosure, which undermines the assumption that a lack of reported attacks leaves time to wait. Teams mid-upgrade to Cloud Foundation 9.1.1 also face a sequencing conflict that forces a choice before they patch.
What to do
- Patch vCenter to the fixed version for your branch as an emergency change.
- Check whether you are on vCenter 8.0 U3m or 9.0.2.0200 before planning a Cloud Foundation 9.1.1 upgrade.
- Treat vSphere 6.5, 6.7 and 7.0 as affected and request an extended support patch for 7.0 if eligible.
- Review your own network defences around vCenter, since Broadcom lists no workaround.