Broadcom has issued patches for a series of VMware vulnerabilities—one of which is exceptionally dangerous: a flaw allowing anyone with network access to a vCenter server to bypass authentication altogether. The advisory, VMSA-2026-0009, covers vCenter, SDDC Manager, and VMware Tools, with CVSS scores ranging from 6.7 to 9.8. The worst of them, CVE-2026-123890, scores 9.8 and lives in VMware Directory Service. No login or valid credentials are required for that bypass.
What’s at Risk
vCenter is the central management hub for all virtual infrastructure—the place where hosts, storage, networks, and VMs are controlled. With administrative access here, an attacker could alter settings, provision new accounts, and access virtual disk content. The bypass flaw was reported to Broadcom by Mandiant. Although it resides in the same directory service as a similar July disclosure (CVE-2026-59309), researchers say it is a distinct issue. There’s currently no evidence of active exploitation, but precedent—from exposed servers being rapidly scanned and web-shell campaigns using prior bugs—suggests risk is high.
Other Flaws and Patch Guidance
Besides the authentication bypass, there are three serious vulnerabilities in SDDC Manager: an SQL injection (CVE-2026-123891, score 8.1), a command injection (CVE-2026-123892, score 7.2), and a local privilege escalation bug (CVE-2026-123893, score 6.7). All were reported by NATO’s NCSC. Meanwhile, VMware Tools for Windows has its own issue: a SAML token signature bypass (CVE-2026-123894, score 6.7), letting a user with local privileges escalate within a virtual machine.
To defend, Broadcom released updated builds packed with fixes. For vCenter, vSphere Foundation and Cloud Foundation users should move to version 9.1.1.0200, 9.0.2.0200, or 8.0 U3m. Cloud Foundation 5.x users should patch to 5.2.5, and customers using Telco Cloud should consult KB463116. Notably, vCenter 7.0 doesn’t yet have a public patch—those with extended support must reach out to Broadcom. SDDC Manager users should upgrade to 9.1.1.0200 or 9.0.2.0100; VMware Tools for Windows needs to hit version 13.1.5.0 or 12.5.5.
What Administrators Should Do Now
Since the flaw currently has no workaround, applying patches is the only viable mitigation. Teams should scan their environments to identify all vCenter instances, especially those exposed to untrusted networks. Access should be restricted to trusted administrator IPs. Security teams should also monitor for abnormal logins, newly created accounts, or unexpected permission changes. Those running version 7.0 must contact Broadcom if they hold extended support agreements.
This vulnerability disclosure underlines how central vCenter is to virtual infrastructure security. With attackers rapidly weaponizing even recently disclosed bugs, organizations must treat every surface as critical—not just what seems exposed. The lessons here are clear: patch aggressively, restrict access tightly, and assume that vulnerabilities won’t stay dormant for long.