Protect.Computer
NEWS

VMware vCenter Auth Bypass CVE-2026-123890 (CVSS 9.8) Patched

· 3 min read · Got hacked Network safety
VMware vCenter Auth Bypass CVE-2026-123890 (CVSS 9.8) Patched

Broadcom, which owns VMware, published advisory VMSA-2026-0009 on November 19 for a critical flaw in VMware vCenter, the console many organizations use to manage their ESX hosts and virtual machines. Tracked as CVE-2026-123890 and rated CVSS 9.8, it is an authentication bypass in the VMware Directory Service: an attacker with network access to vCenter can get in without valid credentials, according to The Hacker News. The Hacker News says credit for reporting the bug goes to Google-owned Mandiant, and that the advisory does not say what level of access an attacker gains after the bypass.

Broadcom’s own FAQ for the advisory says the vCenter issue “qualifies under ITIL methodologies as an emergency change.” The Hacker News says Broadcom has reported no attacks and no public exploit code. The advisory FAQ says the flaw is separate from CVE-2026-59309, an earlier vCenter authentication bypass in VMSA-2026-0006. The Hacker News notes attackers began exploiting a different July vCenter flaw, a directory-traversal bug, about five days after disclosure, per the German incident response firm QUIRSO. Broadcom lists no workaround: asked whether one exists, its FAQ answers “Not as listed by Broadcom.”

The advisory covers four other flaws, rated 6.7 to 8.1 per The Hacker News: a SQL injection (CVE-2026-123891), a command injection (CVE-2026-123892) and a local privilege escalation (CVE-2026-123893) in SDDC Manager, and a SAML token signature bypass in VMware Tools for Windows (CVE-2026-123894) that only applies where Guest Alias mapping is configured. Broadcom says none of them allows code to run on an ESX host from inside a virtual machine, and ESX itself is not affected.

How to check if you’re affected

Affected products are VMware vCenter 8.0, 9.0 and 9.1, plus the vCenter builds shipped inside VMware Cloud Foundation (including 5.x), vSphere Foundation, Telco Cloud Platform and Telco Cloud Infrastructure, per The Hacker News. Broadcom’s FAQ says to presume vCenter on vSphere 6.5 and 6.7 is affected, since it no longer evaluates versions past end of support, and that vSphere 7.0 is affected too; 7.0 customers with an extended support contract can request a patch through those channels. The flaw is present whether or not Enhanced Linked Mode is in use.

  • Fixed vCenter versions: Broadcom’s FAQ names vCenter 8.0 U3m for the 8.0 line (Cloud Foundation 5.x customers apply it through the asynchronous patching process in KB 88287) and 9.0.2.0200 for the 9.0 line. We did not read the advisory’s fixed build for the 9.1 line; take it from VMSA-2026-0009. Patches are cumulative, so the fixed versions also contain the fixes for VMSA-2026-0008.
  • SDDC Manager: the fixed versions are 9.1.1.0200 for 9.1.x, 9.0.2.0100 for 9.0.x and 5.2.5 for 5.x.
  • Applying the update: The Hacker News says the updates are cumulative and cannot be installed through vCenter Quick Patch, that virtual machines keep running during the install while management access drops briefly, and that some encryption operations against a Standard Key Provider are unavailable until vCenter is back.
  • Upgrade conflict: Broadcom says installing vCenter 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VMware Cloud Foundation 9.1.1 (a “Back-in-Time” restriction). If you are mid-upgrade, its 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.
  • VMware Tools for Windows: Broadcom’s FAQ says to check that Windows VMs in Cloud Foundation environments run a fixed VMware Tools version and describes guest aliases as part of the VGAuth service; consult the advisory for the fixed Tools version.

Related earlier coverage: Five VMware Flaws: Auth Bypass, RCE, and VM Escape in vCenter and China-linked hackers exploit VMware vCenter flaw, deploy ransomware.

Sources

Related reading