Is your vCenter still unpatched for CVE-2026-123890?
Broadcom published VMSA-2026-0009 on 19 November 2026. CVE-2026-123890 is an authentication bypass in the VMware Directory Service (vmdir) in vCenter. Broadcom scores it CVSS 3.1 9.8 Critical. An attacker with network access, and no credentials, can bypass authentication and gain unauthorised access to the system. Broadcom does not describe that access in more detail. Upgrade to a fixed build now. Broadcom lists no workaround.
Critical (CVSS 3.1 9.8, Broadcom). Published 19 November 2026
VMSA-2026-0009 is dated 19 November 2026. The CVE record was published at 14:02 GMT the same day, and lists CWE-288. NVD published the record at 15:17 GMT. No exploitation reported as of 19 Nov 2026. The identifier was not in CISA KEV when we checked at 16:06 GMT on 19 November 2026 (catalogue 2026.11.18). Absence from that catalogue is not a finding that the flaw has not been exploited. Reported by The Hacker News, Broadcom has not reported attacks or public exploit code. ESX is not affected.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 19 November 2026, 16:06 GMT.
At a Glance
Based on Broadcom's VMSA-2026-0009 and its FAQ, the CVE record published at 14:02 GMT on 19 November 2026, the NVD record published at 15:17 GMT, and a CISA KEV check at 16:06 GMT on 19 November 2026. Last updated 19 November 2026, 16:06 GMT.
Critical (CVSS 3.1 9.8, Broadcom)
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, scored by Broadcom and published in the NVD record. The CVE record lists CWE-288 (authentication bypass using an alternate path or channel). Network accessible, no privileges and no user interaction required.
Fix released today
Upgrade vCenter to 9.1.1.0200 (build 25901347), 9.0.2.0200 (build 25901331) or 8.0 U3m (appliance version 8.0.3.01200, build 25934264), or VMware Cloud Foundation 5.x to 5.2.5. Broadcom lists no workaround. Broadcom's FAQ says the update is not eligible for vCenter Quick Patch.
Supported vCenter branches, plus older releases
vCenter 9.1.x, 9.0.x and 8.0, including builds in VMware Cloud Foundation and vSphere Foundation, plus VCF 5.x. 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 (KB463116). vSphere 7.0 is listed as affected. Presume 6.5 and 6.7 are affected. ESX is not affected.
None reported
No exploitation reported as of 19 Nov 2026. Not in CISA KEV (catalogue 2026.11.18, checked 16:06 GMT). The earlier July path-traversal issue CVE-2026-59310, in vCenter's Syslog server, is already in that catalogue.
In July 2026 Broadcom patched CVE-2026-59309, an authentication bypass in the VMware Directory Service, and CVE-2026-59310, a path-traversal issue in vCenter's Syslog server, under VMSA-2026-0006. CVE-2026-123890 is a new and distinct issue.
CISA adds CVE-2026-59310, the path-traversal issue in vCenter's Syslog server, to the Known Exploited Vulnerabilities catalogue. CISA records known ransomware campaign use for that CVE.
Broadcom publishes VMSA-2026-0009. The advisory and its FAQ are dated 19 November 2026. The CVE record is published at 14:02 GMT, and lists CWE-288.
NVD publishes CVE-2026-123890, with Broadcom's CVSS 3.1 9.8 score and the same fixed versions.
What to Do in the Next 24 Hours
Vendor advice and our advice are labelled separately. Tick both tracks.
Apply the fixed builds. There is no vendor workaround
- Upgrade vCenter to 9.1.1.0200 (build 25901347), 9.0.2.0200 (build 25901331) or 8.0 U3m (8.0.3.01200, build 25934264). For VMware Cloud Foundation 5.x, apply vCenter 8.0 U3m by asynchronous patch (KB88287), then update SDDC Manager to 5.2.5. Telco Cloud Platform and Telco Cloud Infrastructure are fixed through 8.0 U3m (KB463116).
- Broadcom lists no workaround. The FAQ says the vCenter issue qualifies as an emergency change under ITIL.
- Broadcom's FAQ says these vCenter updates are not eligible for vCenter Quick Patch. Virtual machines continue to run during the update, but management access drops briefly.
- Broadcom's FAQ says installing 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VCF 9.1.1 (a Back-in-Time restriction). Upgrade vCenter to 9.1.1 first and apply the security update there, or wait for VCF 9.1.2.
- vSphere 7.0 reached End of General Support on 2 October 2025. If you have an extended support contract, request a patch through that process. Presume vSphere 6.5 and 6.7 are affected, and plan to replace them.
Prioritise exposed vCenters, restrict management paths, then hunt
- Treat this as an emergency change. Patch internet-facing and MSP-managed client vCenters first.
- Restrict the vCenter management interface (TCP 443) and vmdir LDAP (TCP 389 and 636) to a management VLAN or jump hosts. This reduces exposure. It is not a Broadcom workaround or a substitute for the update.
- Inventory every vCenter, including 6.5, 6.7 and 7.0. Isolate or replace those older releases.
- Confirm that vCenter backups are offline and immutable.
- Hunt for the signs in Our advice below. If you suspect compromise, isolate vCenter, rotate SSO, administrator@vsphere.local and service-account credentials, rebuild from known-good media, and engage incident response.
Proactive: Find Exposure and Patch
Vendor advice is labelled where we are repeating Broadcom's own guidance. Inventory, prioritisation and network restrictions are our advice.
Inventory every vCenter
Our advice is to search management networks, VMware Cloud Foundation and vSphere Foundation estates, Telco deployments, and MSP-managed client sites for vCenter. Record the running version and build from the vSphere Client Summary tab or PowerCLI. Include 6.5, 6.7 and 7.0, even where official support has ended.
Prioritise internet-facing and client-managed appliances
Our advice. Start with any vCenter whose management interface or LDAP ports are reachable from untrusted networks, then MSP-managed client vCenters. Enhanced Linked Mode does not change exposure: Broadcom says the issue is present whether or not you use it.
Upgrade to the fixed builds
This is the vendor fix. Apply 9.1.1.0200 (build 25901347), 9.0.2.0200 (build 25901331) or 8.0 U3m (8.0.3.01200, build 25934264) for vCenter, or 5.2.5 for VMware Cloud Foundation 5.x. VCF 5.x customers apply vCenter 8.0 U3m through the asynchronous patching process in KB88287, and update SDDC Manager to 5.2.5. Telco Cloud Platform and Telco Cloud Infrastructure are fixed through 8.0 U3m (KB463116). Patches are cumulative. Confirm the running build after the update.
Plan around Quick Patch and upgrade conflicts
Vendor advice, from Broadcom's FAQ. These vCenter updates cannot be installed through vCenter Quick Patch. If you are mid-upgrade to VCF 9.1.1, installing 8.0 U3m or 9.0.2.0200 will block that path. Upgrade vCenter to 9.1.1 first and apply the security update there, or wait for VCF 9.1.2. Until the patch is in, our advice is still to restrict TCP 443, 389 and 636 to management paths only.
Affected products and fixed versions (Broadcom)
Figures below are from VMSA-2026-0009. Scores are CVSS 3.1, as published by Broadcom.
| Product | Affected | Fixed version |
|---|---|---|
| vCenter in VMware Cloud Foundation or vSphere Foundation | 9.1.x | 9.1.1.0200, build 25901347 |
| vCenter in VMware Cloud Foundation or vSphere Foundation | 9.0.x | 9.0.2.0200, build 25901331 |
| VMware vCenter | 8.0 | 8.0 U3m (8.0.3.01200, build 25934264) |
| VMware vCenter | 7.0 | Contact Broadcom Support if you have an extended support contract |
| VMware Cloud Foundation | 5.x | 5.2.5 (apply 8.0 U3m by async patch, KB88287, then SDDC Manager 5.2.5) |
| VMware Telco Cloud Platform | 3.0, 4.x, 5.0.x, 5.1.x, 5.2 | 8.0 U3m (KB463116) |
| VMware Telco Cloud Infrastructure | 3.0 | 8.0 U3m (KB463116) |
| VMware vSphere 6.5 and 6.7 | Not evaluated in the advisory. Broadcom says presume they are affected | Upgrade to a supported fixed release |
ESX is not affected. Broadcom also says none of the issues in this advisory permit code execution on an ESX host from inside a virtual machine.
Other issues in the same advisory
VMSA-2026-0009 also fixes four lower-severity flaws that need prior access. They are not a substitute for the vCenter update, and they do not change the Critical rating of CVE-2026-123890.
- CVE-2026-123891, Important 8.1: SQL injection in SDDC Manager. An authenticated attacker can perform unauthorised database reads or writes. Fixed in 9.1.1.0200 for 9.1.x, 9.0.2.0100 for 9.0.x, and 5.2.5 for 5.x.
- CVE-2026-123892, Important 7.2: authenticated command injection in SDDC Manager. The 9.0.x fix is 9.0.2.0100, as above.
- CVE-2026-123893, Moderate 6.7: local privilege escalation to root on the SDDC Manager appliance, for an attacker who already has administrative privileges. The 9.0.x fix is 9.0.2.0100, as above.
- CVE-2026-123894, Moderate 6.7: SAML token signature bypass in VMware Tools for Windows, where Guest Alias mapping is configured. An attacker with access to a local privileged process can elevate privileges inside that guest. The issue stays inside the virtual machine. Fixed in VMware Tools 13.1.5.0 (13.x), 12.5.5 (12.x and 11.x), or 12.4.10 for 32-bit Windows.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Check exposure offline and hunt for signs of misuse. Everything is read-only.
check-vcenter-123890.sh
A read-only, offline bash checker. It takes a version string, a build, PowerCLI output or a CSV, and reports FIXED, AFFECTED, REVIEW OR UNKNOWN, or EOS PRESUMED AFFECTED. It treats vCenter 7.0 as affected, as Broadcom lists it, and treats 6.5 and 6.7 as presumed affected, as Broadcom's FAQ says you should presume they are. It never uses the network, never writes a file and never prints extra columns.
bash check-vcenter-123890.sh --version-string 8.0.3.01200 --build 25934264Check-Vcenter123890.ps1
The same checks in PowerShell, with the same options, output and exit codes. Use it against a saved PowerCLI export or a CSV of versions and builds.
pwsh -NoProfile -File .\Check-Vcenter123890.ps1 --file vcenters.csv8 KQL hunts and 4 Sigma rules
8 KQL hunts for Microsoft Sentinel and Microsoft Defender XDR, and 4 Sigma rules, covering vCenter 443 and vmdir LDAP reached from outside management ranges, SSO account changes, ESX service access (including SSH), mass virtual-machine power-offs, snapshot removal, and hosts that stop sending syslog. All of these hunts and rules are our patterns, not vendor signatures. Some syslog hunts use terms Broadcom does not document as forwarded log text, so check your own lines before relying on them. The pack README has the full notes.
Sigma rules (our pattern):
Reactive: How to Hunt (Our Advice)
The hunts below are CybaVerse advice, not vendor advice. Broadcom's advisory describes the flaw and the official fixes. It does not publish a hunt list or indicators of compromise, and this page invents none.
Look for tokens issued without a matching login
Review vCenter vmdir, SSO/sts and vpxd logs for token issuance that has no matching user login. A token appearing without an expected authentication event is a lead, not proof of compromise on its own.
Look for new SSO users and admin group changes
Check for new SSO accounts, unexpected additions to administrator groups, and other identity changes around the vCenter Single Sign-On domain.
Look for unusual LDAP binds and VCSA access
Review unexpected LDAP binds to vmdir, and look for new local accounts or SSH being enabled on the vCenter Server Appliance.
Look at attached ESXi hosts
Even though ESX is not affected by this advisory, a compromised vCenter can still be used against hosts. Watch for SSH or the ESXi shell being enabled, mass virtual-machine power-offs, and snapshot deletion.
Isolate, rotate, rebuild
Our advice: isolate vCenter and keep its logs. Rotate SSO, administrator@vsphere.local and service-account credentials. Rebuild from known-good media, and engage incident response. Updating vCenter on a compromised appliance does not remove an attacker who is already in.
How CybaVerse helps
CybaOps brings proactive checks, reactive hunting and the fix into one service through our FAFO model: Found, Analysed, Fix, Operated.
Find every vCenter
We help you inventory vCenter across your own estate and the client estates you manage, including older 6.5, 6.7 and 7.0 appliances that are easy to miss.
Hunt the signs that matter
UK-based analysts run the hunts above against vCenter and ESXi telemetry, and tune them to your environment so you are not left with an unused query pack.
Drive the update through to a verified build
CybaOps drives remediation, including the emergency vCenter update and any follow-on recovery, through to a verified fix rather than leaving a ticket open after the advisory is acknowledged.
Keep watching after the patch
Analysts monitor alerts 24/7 and act on pre-approved response actions, so the same team that helped you patch can keep watching for later misuse of vCenter.
VMware vCenter CVE-2026-123890 FAQ
Short answers based on Broadcom's VMSA-2026-0009 and FAQ, the CVE record, the NVD record, and a CISA KEV check at 16:06 GMT on 19 November 2026. Last updated 19 November 2026, 16:06 GMT.
Am I affected?
Yes if you run vCenter 9.1.x, 9.0.x or 8.0, including the builds inside VMware Cloud Foundation and vSphere Foundation, or VMware Cloud Foundation 5.x. 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. vSphere 7.0 is listed as affected. Broadcom says you should presume vSphere 6.5 and 6.7 are affected. The issue is present whether or not you use Enhanced Linked Mode. ESX is not affected.
What is the severity?
Broadcom rates CVE-2026-123890 Critical at CVSS 3.1 9.8, with the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The CVE record lists CWE-288. An attacker with network access, and no credentials, can bypass authentication and gain unauthorised access to the system. Broadcom does not describe that access in more detail. The same advisory also fixes four lower-severity issues in SDDC Manager and VMware Tools for Windows, scored between 6.7 and 8.1, which need prior access.
Has this been exploited?
No exploitation reported as of 19 Nov 2026. CVE-2026-123890 was not in CISA's Known Exploited Vulnerabilities catalogue when we checked at 16:06 GMT on 19 November 2026 (catalogue version 2026.11.18, released 19:17 GMT on 18 November 2026). Absence from that catalogue is not a finding that the flaw has not been exploited. Reported by The Hacker News, Broadcom has not reported attacks or public exploit code. The earlier July path-traversal issue CVE-2026-59310, in vCenter's Syslog server, is already in that catalogue, and CISA records known ransomware campaign use for that CVE. Broadcom's FAQ says CVE-2026-123890 is a new and distinct issue from CVE-2026-59309.
What are the fixed versions?
vCenter 9.1.1.0200 (build 25901347), 9.0.2.0200 (build 25901331) or 8.0 U3m (8.0.3.01200, build 25934264), or VMware Cloud Foundation 5.2.5. VCF 5.x customers apply vCenter 8.0 U3m using the asynchronous patching process in KB88287, and update SDDC Manager to 5.2.5. Telco Cloud Platform and Telco Cloud Infrastructure are fixed through 8.0 U3m (KB463116). Patches are cumulative. Confirm the running build after you update.
Is there a workaround?
No. VMSA-2026-0009 lists the workaround as none, and Broadcom's FAQ says there is not a workaround as listed by Broadcom. Restricting TCP 443, 389 and 636 to a management VLAN or jump hosts is our advice to reduce exposure until you can update. It is not a vendor fix.
Is ESX affected?
No. Broadcom's FAQ says ESX is not affected by this VMSA, and that none of the issues permit code execution on an ESX host from a virtual machine. A compromised vCenter can still be used against attached hosts, so our advice is still to watch ESXi for SSH or shell being enabled, mass virtual-machine power-offs and snapshot deletion.
What about vSphere 6.5, 6.7 and 7.0?
vSphere 7.0 is listed in the advisory as affected. It reached End of General Support on 2 October 2025. If your organisation has an extended support contract, request a patch through that process. For 6.5 and 6.7, Broadcom does not evaluate products past End of General Support and says you should presume they are affected. Our advice is to isolate or replace those appliances and move to a supported fixed release.
Will this block a VCF 9.1.1 upgrade?
Yes, if you install vCenter 8.0 U3m or 9.0.2.0200 and then try to move to VCF 9.1.1. Broadcom's FAQ says those updates block upgrades to VCF 9.1.1 (a Back-in-Time restriction), and that the vCenter updates in this advisory are not eligible for vCenter Quick Patch. The options are to upgrade vCenter to 9.1.1 first and apply the security update there, or to wait for VCF 9.1.2.
What should I do if I suspect compromise?
This is our advice, not vendor advice. Isolate vCenter and keep its logs. Rotate SSO, administrator@vsphere.local and service-account credentials. Rebuild from known-good media, and engage incident response. Updating vCenter on a compromised appliance does not remove an attacker who is already in.
Need help finding vCenter across the estates you manage?
CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions, and CybaOps drives remediation through to a verified fix, so proactive checks and reactive response happen in one place.
Sources
- Broadcom VMSA-2026-0009, VMware vCenter, Tools, and SDDC Manager updates (dated 19 November 2026)
- Broadcom VMSA-2026-0009 Questions and Answers (initial advisory, published 19 November 2026)
- CVE record for CVE-2026-123890 (published 14:02 GMT on 19 November 2026; CWE-288)
- NVD record for CVE-2026-123890 (published 15:17 GMT on 19 November 2026)
- vCenter 9.1.1.0200 release notes (build 25901347, 19 November 2026)
- vCenter 9.0.2.0200 release notes (build 25901331, 19 November 2026)
- vCenter 8.0 Update 3m release notes (8.0.3.01200, build 25934264, 19 November 2026)
- Broadcom KB 88287, cited in VMSA-2026-0009 and its FAQ for VMware Cloud Foundation 5.x asynchronous patching
- Broadcom KB 463116, Telco Cloud response to VMSA-2026-0009 (fixed through vCenter 8.0 U3m)
- NVD record for CVE-2026-59310, placing the July path-traversal issue in vCenter's Syslog server
- CISA Known Exploited Vulnerabilities catalogue (checked 16:06 GMT on 19 November 2026; catalogue version 2026.11.18). CVE-2026-59310 remains in the catalogue, with known ransomware campaign use recorded by CISA.
- The Hacker News, 19 November 2026, for the note that Broadcom has not reported attacks or public exploit code