VMWare vCenter Authentication Bypass Using an Alternate Path or Channel Vulnerability
TL;DR 📌
- Broadcom VMware vCenter contains an authentication bypass using an alternate path or channel vulnerability in the VMware Directory Service that allows an unauthenticated attacker with network access to vCenter to bypass authentication and gain unauthorized access to the system.
- Highest CVSS: 9.8 (Critical).
- Listed in CISA KEV (2026-11-20) — this is being exploited in the wild.
- Check the advisory for fixed releases — remediation detail is in the vendor link below.
- CVEs: CVE-2026-123890.
What it is
CVE-2026-123890 is an authentication bypass in the VMware Directory Service (vmdir), the component in vCenter that handles identity and authentication across a vSphere deployment. The flaw lets an unauthenticated attacker with network access to vCenter bypass authentication entirely and gain unauthorized access to the system — no credentials or user interaction required.
The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms this is reachable remotely over the network, with low attack complexity, no privileges and no user interaction needed. Given vmdir’s role, successful exploitation gives an attacker a foothold in the management plane for the vCenter instance and the infrastructure it controls — the impact ratings (C:H/I:H/A:H) indicate full compromise of confidentiality, integrity and availability.
This affects vCenter Server across multiple release lines: 9.1.x, 9.0.x, 8.0, and 5.x, plus Telco Cloud Platform (versions 3.0, 4.x, 5.0.x, 5.1.x, 5.2) and Telco Cloud Infrastructure 3.0. Fixes exist for 9.1.1.0200, 9.0.2.0200, 8.0 U3m, and 5.2.5; Telco Cloud customers should consult KB463116 for their specific remediation path.
The vulnerability is listed in CISA’s Known Exploited Vulnerabilities catalogue, added on 2026-11-20.
What to do
- Patch vCenter to the fixed release for your branch: 9.1.1.0200 (from 9.1.x), 9.0.2.0200 (from 9.0.x), 8.0 U3m (from 8.0), or 5.2.5 (from 5.x). Treat this as urgent given KEV listing and the CVSS 9.8 rating.
- For Telco Cloud Platform (3.0, 4.x, 5.0.x, 5.1.x, 5.2) and Telco Cloud Infrastructure 3.0, follow the remediation steps in KB463116 rather than the standard vCenter fix path.
- Restrict network access to vCenter’s management interfaces to trusted administrative networks only — this reduces exposure while patching is scheduled, given the bypass requires only network reachability to vmdir, not credentials.
- After patching, review vCenter authentication and access logs for anomalous activity predating the update, since the flaw permits unauthenticated access and could have gone unnoticed.
- Confirm your vCenter version against the exact affected ranges above before assuming you’re clear — point releases within 9.1.x, 9.0.x, 8.0 and 5.x not matching the fixed builds remain vulnerable.
For leadership 🧭
Executive summary. This flaw lets anyone with network access to vCenter skip authentication altogether and take full control of the virtualisation management plane, with no credentials needed. It is already listed in CISA’s KEV catalogue, so patching should be treated as an immediate priority rather than scheduled for a routine window.
Why it matters:
- vmdir is the identity and authentication backbone for vSphere; bypassing it gives an attacker control of vCenter itself, not just a single VM or host
- The CVSS vector shows network-only access is sufficient with no privileges or user interaction, meaning exposure depends on who can reach vCenter’s management interface, not on credential strength or user behaviour
- Impact covers confidentiality, integrity and availability in full, so a successful bypass could mean silent reconfiguration, data exposure or disruption across everything vCenter orchestrates
- Telco Cloud Platform and Telco Cloud Infrastructure deployments are also affected and need their own remediation path via KB463116 rather than the standard vCenter patch
Now / Next / Later:
- Now: Identify every vCenter instance and its exact build number across 9.1.x, 9.0.x, 8.0 and 5.x, and restrict network reach to management interfaces to trusted admin networks immediately.
- Next: Patch each instance to its fixed build (9.1.1.0200, 9.0.2.0200, 8.0 U3m, or 5.2.5), or follow KB463116 for Telco Cloud Platform and Telco Cloud Infrastructure, in the next available change window given the KEV listing and 9.8 severity.
- Later: Review vCenter authentication and access logs for anomalous activity predating the patch, and establish a standing process to track vCenter point releases against vendor-confirmed fixed builds rather than assuming a branch is current.