VMware vCenter Has a 9.8 Authentication Bypass (CVE-2026-123890). No Workaround, No Reported Attacks Yet. Patch to 8.0 U3m, 9.0.2.0200 or 9.1.1.0200
If you run VMware vCenter, schedule the update now. Broadcom published VMSA-2026-0009 on Thursday, November 19, 2026. It fixes CVE-2026-123890, an authentication bypass in the VMware Directory Service inside vCenter, scored 9.8 on CVSS v3.1. Broadcom lists no workaround. The fixed versions are:
vCenter 9.1.x (VMware Cloud Foundation and vSphere Foundation): 9.1.1.0200
vCenter 9.0.x (VMware Cloud Foundation and vSphere Foundation): 9.0.2.0200
vCenter 8.0: 8.0 U3m
VMware Cloud Foundation 5.x: 5.2.5. Broadcom's Q&A says VCF 5.x customers apply vCenter 8.0 U3m through the asynchronous patching process in KB 88287, and update SDDC Manager to 5.2.5.
vCenter 7.0: no public fix. The advisory says to contact Broadcom Support if you have an extended support contract. vSphere 7 left general support on October 2, 2025.
vCenter 6.5 and 6.7: not evaluated. Broadcom's Q&A says to presume they are affected.
Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x and 5.2, and Telco Cloud Infrastructure 3.0, are also affected. Broadcom points those customers to KB463116.
Until you can patch, the one thing you control is who can reach vCenter on the network. Broadcom's own description of the attack starts with "a malicious actor with network access to vCenter." vCenter should never face the internet, and the fewer internal hosts that can reach it, the smaller the pool of attackers.
What Broadcom says
The advisory text: "VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service." The known attack vector: "A malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system."
The CVSS vector is AV:N/AC:L/PR:N/UI:N. That means over the network, low complexity, no login and no user action needed. The weakness is CWE-288, authentication bypass through an alternate path or channel.
Workarounds: "None." The Q&A adds that firewall rules and other controls in your own environment may help, and that each organization has to decide whether to rely on them.
Enhanced Linked Mode does not matter here. The Q&A says the flaw is in vCenter itself and is present whether or not you use ELM.
Updating vCenter does not stop running workloads. The vSphere Client and other management tools go away briefly during the update. These updates are not eligible for vCenter Quick Patch. The VAMI works.
Credit for the report goes to Mandiant.
One upgrade trap
Broadcom's Q&A warns that vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1. Broadcom calls this a "Back-in-Time" restriction and says customers should wait briefly for VCF 9.1.2. If you are partway through an upgrade, the Q&A gives two choices: move vCenter to 9.1.1 first and apply the 9.1.1.0200 fix there, or wait and do the prerequisite upgrades (VCF Operations, NSX Managers) in the meantime.
If you run a third-party engineered system such as Dell VxRail or HPE SimpliVity, Broadcom says to get guidance from that vendor first.
Am I affected?
Check the version of every vCenter you run, including the ones inside Cloud Foundation and vSphere Foundation.
In the vSphere Client, open the vCenter and read the version and build on the Summary tab.
In PowerCLI, after Connect-VIServer, read $global:DefaultVIServer.Version and $global:DefaultVIServer.Build.
You are affected if you see any of these:
9.1 anything below 9.1.1.0200
9.0 anything below 9.0.2.0200
8.0 at any update below Update 3m (8.0 U3m)
7.0, 6.7 or 6.5 at any version
Broadcom's Q&A puts it plainly: "If you have a question about whether you are affected, it is likely that you are and should take action immediately."
Then check reachability. List every network that can reach your vCenter appliance. If the answer includes the internet, a guest VPN pool, or general user subnets, close that first. Broadcom's port reference is at ports.broadcom.com.
The other four bugs in the same advisory
VMSA-2026-0009 covers five CVEs in total. The other four score between 6.7 and 8.1.
CVE-2026-123891 (SQL injection), CVE-2026-123892 (authenticated command injection) and CVE-2026-123893 (local privilege escalation to root) are in SDDC Manager. Fixed in 9.1.1.0200, 9.0.2.0100 and 5.2.5.
CVE-2026-123894 is a SAML token signature bypass in VMware Tools for Windows, inside guests that use guest alias mapping. Fixed in VMware Tools 13.1.5.0 and 12.5.5. Stopping or removing VMware Tools is not a workaround, per the Q&A.
ESX, NSX, VCF Operations, VCF Automation, Workstation and Fusion are not affected, per the Q&A.
What is not known
Whether anyone is exploiting it. The advisory makes no statement about exploitation. The Hacker News reports that Broadcom has not reported any attacks or any public exploit code.
It is not in CISA's Known Exploited Vulnerabilities catalog. The catalog we checked is version 2026.11.18, released November 18 at 19:17 UTC, before this advisory was published.
How Mandiant found it. The advisory thanks Mandiant for the report and says nothing more.
Which network service or port the attack uses. The advisory names the VMware Directory Service but publishes no port, request path or technical detail.
Indicators of compromise. None were published in the sources we read, so we added nothing to our feed.
Some history to weigh: CISA's catalog already lists 12 vCenter CVEs as exploited, including CVE-2026-59310 from July. In July, exploitation started five days after Broadcom's disclosure. That is not evidence about this flaw. It is a reason not to wait for one.
How we know
We read Broadcom's advisory VMSA-2026-0009 on support.broadcom.com and quoted its response matrix. We read Broadcom's VMSA-2026-0009 Questions and Answers document on the VMware GitHub (vcf-security-and-compliance-guidelines) for the upgrade trap, the VCF 5.x path and the older-version guidance. We read the CVE record from CVE.org and NVD, published November 19, 2026, which carries the 9.8 score, the vector and the same fixed versions. We downloaded CISA's KEV JSON and searched it for the CVE: no entry.
Our edge did not look for this. The advisory publishes no request path or port, so there is nothing for our edge sensors to match, and a vCenter sits inside your network where our edge does not see it.
Sources
Broadcom, VMSA-2026-0009: support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
Broadcom, VMSA-2026-0009 Questions and Answers: github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md
CVE record CVE-2026-123890: cve.org and nvd.nist.gov
CISA Known Exploited Vulnerabilities catalog, version 2026.11.18
The Hacker News, "Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication," November 19, 2026
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.



Comments