Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication
Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication
A critical flaw in VMware vCenter lets an attacker with network access bypass authentication and gain unauthorized access to the system, Broadcom, which owns VMware, said in an advisory published today.
Fixed versions are out for all supported branches, and the company lists no workaround. vCenter is the central console for managing an organization’s ESX hosts and virtual machines.
The vulnerability is tracked as CVE-2026-123890 and is rated 9.8 on the CVSS scoring system. “VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service,” the advisory says.
In an FAQ published with the advisory, the company says the issue “qualifies under ITIL methodologies as an emergency change,” and urges organizations to consult their security staff immediately on timing.
The company has not reported any attacks exploiting the flaw, or any public exploit code. It also does not say what level of access an attacker gains after the bypass. Credit for reporting the bug goes to Google-owned Mandiant.
The bug is present in vCenter 8.0, 9.0, and 9.1, and in the vCenter builds that ship inside VMware Cloud Foundation, vSphere Foundation, and the Telco Cloud Platform and Telco Cloud Infrastructure products. That includes the older Cloud Foundation 5.x line. It is there whether or not Enhanced Linked Mode is in use.
Older versions are not cleared. The company no longer evaluates versions past end of support, and says vSphere 6.5 and 6.7 should be presumed affected. The same goes for vSphere 7.0, which left general support in October 2025, and whose customers can request a patch under an extended support contract.
None of the five flaws in the advisory lets code run on an ESX host from inside a virtual machine, and ESX itself is not affected, the advisory FAQ says.
There is no fallback for systems that cannot be updated yet: asked whether a workaround exists, the FAQ answers “Not as listed by Broadcom,” while noting that mitigations may still exist in an organization’s own defenses.
The updates are cumulative and cannot be installed through vCenter Quick Patch. Virtual machines continue running while vCenter installs the update, though management access drops briefly, and some encryption operations against a Standard Key Provider become unavailable until vCenter is back online.
One warning applies to upgrades already in progress: installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VMware Cloud Foundation 9.1.1, a conflict the FAQ calls a “Back-in-Time” issue. The options are to upgrade vCenter to 9.1.1 first and apply the security update there, or to wait briefly for VCF 9.1.2.
The bypass is the second critical authentication flaw in the VMware Directory Service this year. The earlier vCenter flaws, patched on July 29, included CVE-2026-59309, another 9.8-rated bypass in the same component per the July advisory, alongside a directory-traversal bug, CVE-2026-59310.
Attacks on that traversal flaw began five days after its disclosure, German incident response firm QUIRSO assessed in August, linking them with moderate confidence to a suspected China-nexus actor.
The August attacks compromised an estimated 361 IP addresses in 47 countries and deployed Babuk-derived ransomware on ESXi hosts. Broadcom has reported no attacks on the new bypass.
The advisory also fixes four lower-severity flaws, rated 6.7 to 8.1: a SQL injection (CVE-2026-123891) and a command injection (CVE-2026-123892) in SDDC Manager, a privilege escalation to root on the SDDC Manager appliance (CVE-2026-123893), and a SAML token signature bypass in VMware Tools for Windows (CVE-2026-123894), exploitable only where Guest Alias mapping is configured. Each needs an authenticated or already privileged actor, and the last one stays inside the guest virtual machine.
