critical severityConfidence highHistorical record

VMware vCenter login bypass: anyone who can reach vCenter on the network can get in without a password (CVE-2026-123890, VMSA-2026-0009)

Direct answer

VMware vCenter login bypass: anyone who can reach vCenter on the network can get in without a password (CVE-2026-123890, VMSA-2026-0009), also tracked as CVE-2026-123890 / VMSA-2026-0009 / vCenter 8.0 U3m is a critical-severity threat campaign HOL Guard tracked from Nov 19, 2026 to Nov 19, 2026, verified against 4 primary sources and last reviewed Nov 19, 2026. Active tracking has ended and the record remains published as a permanent historical research record.

Broadcom published VMSA-2026-0009 on November 19, 2026. The critical issue, CVE-2026-123890 (CVSS 9.8, reported by Mandiant), is an authentication bypass in the VMware Directory Service of vCenter: an attacker with network access to vCenter can gain unauthorized access with no credentials. It is distinct from July's CVE-2026-59309 (VMSA-2026-0006). Fixed builds are vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, and VCF 5.2.5; vCenter 7.0 has no public patch and Broadcom says to presume it is affected. The same advisory fixes three SDDC Manager bugs (CVE-2026-123891 SQL injection, CVE-2026-123892 command injection, CVE-2026-123893 local privilege escalation) and a VMware Tools for Windows SAML signature bypass (CVE-2026-123894). No exploitation reported and not on CISA KEV as of publication.

Also tracked as CVE-2026-123890 · VMSA-2026-0009 · vCenter 8.0 U3m · vCenter 9.0.2.0200 · vCenter 9.1.1.0200 · VCF 5.2.5 · CVE-2026-123891 · CVE-2026-123892 · CVE-2026-123893 · CVE-2026-123894 · VMware Directory Service authentication bypass

First observed
Nov 19, 2026
Last observed
Nov 19, 2026
Last reviewed
Nov 19, 2026
Tracking ended
Nov 19, 2026

Uncertainty and limitations

Read the evidence limits before acting on this record.

Broadcom has published few technical details. Exploitation status can change quickly; earlier vCenter Directory Service bugs were exploited before disclosure. Exposure depends on who can reach vCenter on the network, which HOL cannot see.

  • ESX, NSX, VCF Operations, VCF Automation, Workstation and Fusion are not affected by VMSA-2026-0009.
  • vCenter 7.0 has no public fix.
  • Not known exploited and not on CISA KEV as of 2026-11-19.
  • HOL Guard does not scan vCenter; this campaign is guidance for teams whose AI coding agents, automation or admins hold vCenter credentials.

Guard coverage and policy

What Guard's reviewed assertions do and do not claim for this campaign, and the reviewed starting points for defense.

Not covered, or partially covered

  • not covered

    HOL Guard reviews AI coding agent actions before they run. It does not patch vCenter or filter network traffic; the fix is the vCenter update.

No campaign-specific policy guidance is published.

Safe next step. Campaign guidance is defensive context. It does not auto-apply policy or claim universal campaign coverage.

Timeline

Reviewed events, oldest first, each tied to a verified source.

  1. Disclosure

    Broadcom publishes VMSA-2026-0009 with fixes for CVE-2026-123890 and four other CVEs; no workarounds listed.

    Sources:Broadcom VMSA-2026-0009: VMware vCenter, Tools, and SDDC Manager updates·VMSA-2026-0009 Questions and Answers

  2. Update

    HOL publishes the fix guide with fixed builds per version and the vCenter 7.0 guidance.

    Source:HOL blog: vCenter CVE-2026-123890 fix guide

Publication clock: 14.7 hours from reviewed disclosure timestamp to HOL publication; 12-hour critical target; historical backfill outside target.

Sources

Every claim on this record is traceable to the sources below.

Related reviewed records

Records this one was reviewed against. Every relationship below is part of a released revision, with the reviewer’s stated reason.

Campaign questions, answered

Broadcom published VMSA-2026-0009 on November 19, 2026. The critical issue, CVE-2026-123890 (CVSS HOL Guard tracked the campaign from Nov 19, 2026 to Nov 19, 2026.

No. Active tracking ended Nov 19, 2026; this page remains as a labeled historical research record and does not imply the threat is currently active.

The record cites 4 primary sources, names 0 reviewed artifacts, and was last fully reviewed Nov 19, 2026 by HOL Guard Security Publishing. Its uncertainty and limitations are stated on the record itself.

Campaign guidance is defensive context. It does not auto-apply policy or claim universal campaign coverage.

The permalink above is permanent. The full record can be downloaded from this page as JSON, an artifact CSV, and a STIX 2.1 bundle, and corrections can be requested through the published correction path on the record. Broadcom has published few technical details. Exploitation status can change quickly; earlier vCenter Directory Service bugs were exploited before disclosure. Exposure depends on who can reach vCenter on the network, which HOL cannot see.

Reviewed in full by HOL Guard Security Publishing.

Published
Last full review
Last modified

Report a correction

Record HGTC-2026-BD86BF80