Skip to main content
Menu
CVEs

CVE

VMware vCenter authentication bypass in directory service

Affects VMware vCenter through its Directory Service when an attacker has network access; also lists Telco Cloud Platform and Telco Cloud Infrastructure. Fixed in 9.1.1.0200, 9.0.2.0200, 8.0 U3m and 5.2.5.

CVE-2026-123890Published Updated Summary written by a model

9.8CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 9.1.1.0200, 9.0.2.0200, 8.0 U3m, 5.2.5
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 9.1.1.0200, 9.0.2.0200, 8.0 U3m, 5.2.5.

Summary

An authentication bypass in the VMware Directory Service affects VMware vCenter, as well as VMware Telco Cloud Platform and Telco Cloud Infrastructure. An attacker can exploit it remotely, without logging in, to skip authentication, which could give them full control over the affected systems.

Original description

VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service. Affected versions: 9.1.x (fixed in 9.1.1.0200); 9.0.x (fixed in 9.0.2.0200); 8.0 (fixed in 8.0 U3m); 5.x (fixed in 5.2.5). Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 and Telco Cloud Infrastructure 3.0 are also affected (see KB463116).

Who should check

Teams running VMware vCenter 9.x, 8.0 or 5.x (VCF, vSphere Foundation), plus Telco Cloud Platform and Telco Cloud Infrastructure; 7.0 needs Broadcom Support.

“VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service.”

support.broadcom.com

cve.now Index

41Pcve.now Index 41 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach14/20Affects VMware (an enterprise product or network appliance)
  • Severity9.8/10CVSS 9.8
  • No patch0/5No signal

What would change the score

  • Would score about 86 if added to CISA KEV
  • Would score about 81 if CISA's SSVC rates exploitation active
  • Would score about 46 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 9.1.1.0200, 9.0.2.0200, 8.0 U3m, 5.2.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-123890 (vCenter authentication-bypass vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-123890 (entry last updated 2026-11-19):
Affected:
- VMware VMware vCenter: from 9.1.x, fixed in 9.1.1.0200; from 9.0.x, fixed in 9.0.2.0200; from 8.0, fixed in 8.0 U3m; from 5.x, fixed in 5.2.5
- VMware Telco Cloud Platform: versions 3.0, 4.x, 5.0.x, 5.1.x, 5.2
- VMware Telco Cloud Infrastructure: versions 3.0
Fixed versions: 9.1.1.0200, 9.0.2.0200, 8.0 U3m, 5.2.5.
Conditions (all must be true for the bug to be hit):
- VMware vCenter with the VMware Directory Service is affected (source: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495)
- Attacker must have network access to vCenter (source: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-123890 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123890 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-123890
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123890"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. cve.now early warning

    VMware vCenter flaw CVE-2026-123890 lets network attackers bypass authentication

  4. Posted on X by cve.now

Affected versions

  • VMware VMware vCenter

    From 9.1.x · fixed in 9.1.1.0200; From 9.0.x · fixed in 9.0.2.0200; From 8.0 · fixed in 8.0 U3m; From 5.x · fixed in 5.2.5

  • VMware Telco Cloud Platform

    3.0, 4.x, 5.0.x, 5.1.x, 5.2

  • VMware Telco Cloud Infrastructure

    3.0

Evidence 3

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123890

Is CVE-2026-123890 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

VMware vCenter has an authentication bypass flaw in the VMware Directory Service. An attacker with network access to vCenter can skip authentication and gain unauthorized access to the system.Source: support.broadcom.com

Which versions are affected by CVE-2026-123890?

VMware vCenter: from 9.1.x before 9.1.1.0200; from 9.0.x before 9.0.2.0200; from 8.0 before 8.0 U3m; from 5.x before 5.2.5. Telco Cloud Platform: versions 3.0, 4.x, 5.0.x, 5.1.x, 5.2. Telco Cloud Infrastructure: version 3.0.Source: cve.now feed data

Am I affected, and how do I check?

Listed ranges are 9.1.x (fixed in 9.1.1.0200), 9.0.x (fixed in 9.0.2.0200), 8.0 (fixed in 8.0 U3m) and 5.x (fixed in 5.2.5). Telco Cloud Platform and Telco Cloud Infrastructure are also listed without version ranges. To check, look at the installed vCenter version and build in the vCenter management interface and compare it with these ranges.Source: support.broadcom.com

How do I fix CVE-2026-123890?

Upgrade vCenter to the fixed version for its release line: 9.1.1.0200, 9.0.2.0200, 8.0 U3m or 5.2.5. The facts give no workaround.Source: support.broadcom.com

More CVEs