Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 5 min read

VMware vCenter CVE-2026-123890: CVSS 9.8 Authentication Bypass in Directory Service, No Workaround

TL;DR what: Broadcom disclosed CVE-2026-123890, a CVSS 9.8 authentication bypass in the VMware Directory Service component of vCenter, reported by Mandiant. impact: An attacker with network access can bypass authent

TL;DR

  • what: Broadcom disclosed CVE-2026-123890, a CVSS 9.8 authentication bypass in the VMware Directory Service component of vCenter, reported by Mandiant.
  • impact: An attacker with network access can bypass authentication on the console that manages every ESX host and virtual machine in the environment.
  • fix: Cumulative fixed builds, including vCenter 8.0 U3m and 9.0.2.0200, are out for all supported branches with no workaround, and vSphere 7.0 patches require an extended support contract.
  • who: Organizations running vCenter 8.0, 9.0 or 9.1, VMware Cloud Foundation (including 5.x), vSphere Foundation, Telco Cloud products, or end-of-support vSphere 6.5, 6.7 and 7.0.

Broadcom published an advisory on November 19, 2026 for CVE-2026-123890, a CVSS 9.8 authentication bypass in the VMware Directory Service inside vCenter. An attacker with network access to vCenter can bypass authentication and gain unauthorized access to the console that manages an organization's ESX hosts and virtual machines. Fixed builds are available for every supported branch. Broadcom lists no workaround.

Mandiant reported the bug. Broadcom says it has seen no exploitation and no public exploit code. It also has not said what level of access an attacker gets after the bypass, so defenders have to plan for the worst case: control of the management plane for the whole virtual estate.

What is affected

The flaw is present in vCenter 8.0, 9.0 and 9.1, and in the vCenter builds that ship inside the following products:

  • VMware Cloud Foundation, including the older 5.x line
  • VMware vSphere Foundation
  • VMware Telco Cloud Platform
  • VMware Telco Cloud Infrastructure

The bug is reachable whether or not Enhanced Linked Mode is configured. ESX itself is not affected. According to the advisory FAQ, none of the five flaws in the advisory lets an attacker run code on an ESX host from inside a guest virtual machine.

⚠️ End-of-support versions are presumed vulnerable β€” Broadcom no longer evaluates versions past end of support and says vSphere 6.5 and 6.7 should be presumed affected. The same applies to vSphere 7.0, which left general support in October 2025. Customers on 7.0 can request a patch only under an extended support contract. Without that contract, these deployments have no vendor fix.

Why Broadcom calls it an emergency change

The advisory FAQ says the issue "qualifies under ITIL methodologies as an emergency change" and urges organizations to consult their security staff immediately on timing. 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 update is the only fix Broadcom supports. Until it is applied, how far vCenter is exposed on the network is the main factor an organization controls.

vCenter is a high-value target. One management console controls the compute, storage and networking settings for hundreds or thousands of workloads. A successful attack here does not compromise one server. It can compromise every server the console manages.

Patch mechanics and the Back-in-Time conflict

The updates are cumulative and cannot be installed through vCenter Quick Patch. Virtual machines keep running while vCenter installs the update. Management access drops briefly. Some encryption operations against a Standard Key Provider are unavailable until vCenter is back online.

Organizations in the middle of an upgrade face a sequencing problem. 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. Broadcom gives two options: upgrade vCenter to 9.1.1 first and apply the security update there, or wait briefly for VCF 9.1.2.

Upgrade sequencing affects change planning β€” Teams with a VCF 9.1.1 upgrade already scheduled should account for the Back-in-Time conflict. Applying the 8.0 U3m or 9.0.2.0200 builds now closes the bypass but blocks that upgrade path until VCF 9.1.2 ships.

Second critical bypass in the same component this year

This is the second critical authentication flaw in the VMware Directory Service in 2026. Broadcom's July 29 advisory fixed CVE-2026-59309, another 9.8-rated bypass in the same component, along with a directory-traversal bug, CVE-2026-59310.

Attackers moved quickly on that round. In August, German incident response firm QUIRSO assessed that exploitation of the traversal flaw began five days after disclosure. QUIRSO linked the activity, with moderate confidence, to a suspected China-nexus actor. The campaign compromised an estimated 361 IP addresses across 47 countries and deployed Babuk-derived ransomware on ESXi hosts.

No attacks on CVE-2026-123890 have been reported. The July timeline is the relevant benchmark: a vCenter bug from the same advisory went from disclosure to active exploitation in five days, and the campaign ended with ransomware on hypervisors. A second pre-authentication bypass in the same service, now with a published patch that can be compared against older builds, gives capable actors a clear target.

The other four flaws in the advisory

The advisory also fixes four lower-severity issues rated 6.7 to 8.1:

  • CVE-2026-123891: SQL injection in SDDC Manager
  • CVE-2026-123892: command injection in SDDC Manager
  • CVE-2026-123893: privilege escalation to root on the SDDC Manager appliance
  • CVE-2026-123894: SAML token signature bypass in VMware Tools for Windows, exploitable only where Guest Alias mapping is configured

Each requires an authenticated or already privileged actor, and CVE-2026-123894 stays inside the guest virtual machine. On their own they are not entry points. Their value to an attacker is as follow-on steps once a foothold exists, which is exactly what a management-plane bypass could provide.

RedEye assessment

We rate CVE-2026-123890 as patch-now. Several factors point the same way: a 9.8 network-reachable authentication bypass, no vendor workaround, a repeat flaw in the same directory service, and a recent ransomware campaign that exploited a bug from the July advisory within five days. Broadcom has not released two key facts: what an attacker can do after the bypass, and whether attackers are reverse-engineering the fix. Neither unknown lowers the risk.

The highest exposure sits with organizations still running vSphere 6.5, 6.7 or 7.0 without extended support. Broadcom presumes those versions are affected and offers them no fix. For those environments, the realistic choices are to migrate to a supported branch, buy extended support, or rely on network controls they already have in place. The second-highest exposure is any vCenter interface reachable from networks beyond a tightly restricted management segment.

Originally published on RedEye Threat Intelligence.

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.