Takeaway: On November 19, 2026, Broadcom published VMSA-2026-0009, a Critical security advisory for VMware vCenter, VMware Tools, and SDDC Manager. The advisory covers five privately reported vulnerabilities, including CVE-2026-123890, a vCenter authentication bypass in the VMware Directory Service with a maximum CVSSv3 base score of 9.8. Official workarounds are listed as none. The stated resolution is to install the fixed versions in the advisory’s Response Matrix. The support notification header shows a last update of November 20, 2026, and the status remains OPEN.
The details below come from that advisory and from Broadcom’s supplemental Q&A. Descriptions use the vendor’s own wording and do not include reproduction steps. The official advisory does not say these issues are being exploited in the wild, and this article does not add that claim. Mandiant is credited only as the reporter of CVE-2026-123890.
What the advisory covers
The synopsis is that updates for VMware vCenter, Tools, and SDDC Manager address multiple vulnerabilities: CVE-2026-123890, CVE-2026-123891, CVE-2026-123892, CVE-2026-123893, and CVE-2026-123894. Broadcom rates the advisory Critical. Individual CVSSv3 scores range from 6.7 to 9.8. The introduction says the issues were privately reported and that updates are available to remediate them in affected Broadcom products.
Impacted products listed in the VMSA are VMware vCenter, VMware Cloud Foundation, VMware vSphere Foundation, VMware Tools, VMware Telco Cloud Platform, and VMware Telco Cloud Infrastructure. The Q&A, which is a supplement rather than a substitute for the advisory, says you are affected if you run any version of those components prior to the versions listed as fixed. It also says that if you are unsure, it is likely that you are affected and should take action.
CVE-2026-123890: vCenter authentication bypass
Broadcom’s description is that VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service. The issue is evaluated in the Critical severity range, with a maximum CVSSv3 base score of 9.8. The official known-attack-vector wording is: a malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system. Workarounds are listed as none. Acknowledgments go to Mandiant for reporting the issue.
The Q&A states that CVE-2026-123890 is a new and distinct issue from CVE-2026-59309 in VMSA-2026-0006, and that systems running software below the versions listed in this VMSA still need the update. It also says the vCenter issue is in vCenter itself, not in Enhanced Linked Mode, and is present whether or not you use ELM.
Fixed vCenter versions from the official Response Matrix are:
| Product and version | Fixed version |
|---|---|
| VCF / VVF vCenter 9.1.x.x | 9.1.1.0200 |
| VCF / VVF vCenter 9.0.x.x | 9.0.2.0200 |
| VMware vCenter 8.0 | 8.0 U3m |
| VMware vCenter 7.0 | Contact Broadcom Support if you have an extended support contract. The advisory does not list a 7.0 patch build. |
| VCF vCenter 5.x | 5.2.5, using the asynchronous patching guide in KB 88287 |
| Telco Cloud Platform vCenter 3.0, 4.x, 5.0.x, 5.1.x, 5.2, and Telco Cloud Infrastructure vCenter 3.0 | Follow KB 463116. This article does not invent Telco patch versions. |
SDDC Manager issues and fixed versions
Three of the five CVEs are in SDDC Manager. Broadcom describes CVE-2026-123891 as an SQL-injection vulnerability due to improper sanitization of user-supplied input, rated Important with a maximum CVSSv3 base score of 8.1. The official known-attack-vector wording is that a malicious authenticated actor may exploit this issue by using a specially crafted SQL query to perform unauthorised read/write operations in the database.
CVE-2026-123892 is described as an authenticated command-injection vulnerability due to improper sanitization of user-supplied input, rated Important with a maximum CVSSv3 base score of 7.2. The official wording is that a malicious authenticated actor may exploit this issue to execute arbitrary commands on the appliance.
CVE-2026-123893 is a local privilege-escalation vulnerability, rated Moderate with a maximum CVSSv3 base score of 6.7. The official wording is that a malicious actor with administrative privileges on SDDC Manager may exploit this issue to elevate privileges to root.
All three SDDC Manager issues are credited to Arnoldas Radisauskas of NATO NCSC. Official workarounds are none. The Q&A summarizes the same three outcomes as an authenticated attacker being able to read and write the SDDC Manager database, execute arbitrary commands on the appliance, and, with administrative privileges, elevate privileges to root.
The official SDDC Manager and VCF Installer matrix lists these fixed versions. Do not mix the 9.0 SDDC build with the 9.0 vCenter build: SDDC Manager on 9.0.x.x is fixed in 9.0.2.0100, while vCenter on 9.0.x.x is fixed in 9.0.2.0200.
| Component and version | CVEs | Fixed version |
|---|---|---|
| SDDC Manager 9.1.x.x, and SDDC Manager / VCF Installer 9.1.x.x for CVE-2026-123893 | CVE-2026-123891, CVE-2026-123892, CVE-2026-123893 | 9.1.1.0200. The advisory notes that 123891 and 123892 were first resolved in 9.1.0.0 and 123893 in 9.1.1.0; 9.1.1.0200 is the latest version and contains all three fixes. |
| SDDC Manager and SDDC Manager / VCF Installer 9.0.x.x | CVE-2026-123891, CVE-2026-123892, CVE-2026-123893 | 9.0.2.0100 |
| SDDC Manager 5.x | CVE-2026-123891, CVE-2026-123892, CVE-2026-123893 | 5.2.5 |
CVE-2026-123894: VMware Tools for Windows
Broadcom describes a SAML token signature bypass in VMware Tools for Windows, rated Moderate with a maximum CVSSv3 base score of 6.7. The official known-attack-vector wording is that a malicious actor with access to a local privileged process on a Windows guest VM configured with Guest Alias mapping can exploit this vulnerability to elevate their privileges within the VM. Workarounds are none. The acknowledgment is to Noam Pomerantz.
The official Response Matrix lists VMware Tools 13.x.x.x for Windows as fixed in 13.1.5.0, and VMware Tools 12.3.x for Windows as fixed in 12.5.5. A note on the advisory says VMware Tools 12.4.10, which is part of the 12.5.5 release, also addresses the issue for Windows 32-bit. The Q&A additionally says the issue affects VMware Tools for Windows 13.x, 12.x, and 11.x, and that it is fixed in 13.1.5.0 for 13.x and in 12.5.5 for 12.x and 11.x. Use the VMSA Response Matrix as the source of truth for patch selection. The advisory lists only Tools for Windows; Tools for other guest operating systems is not listed as affected.
The Q&A also says that stopping or removing VMware Tools is not a workaround, and that disabling guest operations is not a workaround for CVE-2026-123894. The recommended response is to update Tools to a fixed version.
What is not listed as affected
The Q&A says ESX, also referred to as ESXi, is not affected by this VMSA. The same document says NSX, VCF Operations, and VCF Automation are not affected. Workstation and Fusion are also not listed as affected. Windows virtual machines running on Workstation or Fusion may still need a fixed VMware Tools build if those VMs could be moved or imported into a VMware Cloud Foundation or vSphere Foundation environment.
This is not a VM escape. The Q&A states that none of the issues in the advisory permit code execution on an ESX host from a virtual machine. CVE-2026-123894 is a privilege escalation that stays inside the Windows guest.
Operational notes from the official Q&A
Broadcom says the vCenter issue qualifies as an emergency change under ITIL methodologies and that organizations should consult their information security staff on timing. Official workarounds are “not as listed by Broadcom.” Compensating controls such as firewalls are an organization’s own decision; Broadcom and VMware Global Support cannot decide that for you. This article does not present network restriction as a vendor workaround.
Patches are cumulative. The Q&A says there is no need to apply VMSA-2026-0008 first, and that the fixed versions in this advisory also contain the fixes for VMSA-2026-0008. Updating vCenter briefly interrupts the vSphere Client and other management methods, but virtual machine and container workloads continue to run. The same is true for an SDDC Manager update: the Q&A says it does not run workloads, so those workloads continue during the update.
These vCenter updates are not eligible for vCenter Quick Patch. The Q&A says the vCenter Appliance Management Interface (VAMI) can be used, through the standard update mechanisms for vSphere and VMware Cloud Foundation. Version information is available in the Summary tab of the vSphere Client; PowerCLI can also report the connected server’s Version and Build. The VMware Tools version is shown in each virtual machine’s Summary tab.
One known issue is a back-in-time upgrade restriction: the Q&A says vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1, and customers should wait for VCF 9.1.2. For older branches, the Q&A says to presume that vSphere 6.5 and 6.7 are affected, because Broadcom does not evaluate products past End of General Support in advisories, and it encourages an upgrade to VCF 9.1. vSphere 7.0 is impacted. It reached End of General Support on October 2, 2025. If you have an active extended support contract, use those processes to request patches; the advisory does not publish a 7.0 fixed build number. On vSphere 8 or VCF 5.x, the fixed vCenter version is 8.0 U3m, which requires the Update 3 lineage. VCF 5.x uses the async patching process in KB 88287, with vCenter 8.0 U3m and SDDC Manager 5.2.5.
These VMware patches sit alongside, rather than instead of, other stack updates. A nginx 1.31.9 security update, the Java4Shell Oracle and OpenJDK updates, or the November 2026 PHP security releases still need to be applied on their own schedules if they apply to your environment.
Key facts
| Item | What official sources say |
|---|---|
| Advisory | VMSA-2026-0009, notification 39495. Issue date November 19, 2026. Support page header last updated November 20, 2026. Status OPEN. Severity Critical. CVSSv3 range 6.7–9.8. Workarounds: none. |
| CVE-2026-123890 | vCenter authentication bypass in the VMware Directory Service, Critical, CVSSv3 9.8. Reported by Mandiant. Official wording: a malicious actor with network access to vCenter may bypass authentication and gain unauthorized access. |
| vCenter fixed versions | 9.1.1.0200 for 9.1.x.x; 9.0.2.0200 for 9.0.x.x; 8.0 U3m for 8.0; 5.2.5 for VCF 5.x. vCenter 7.0: contact Broadcom Support if you have an extended support contract. |
| SDDC Manager CVEs | CVE-2026-123891 (Important, 8.1), CVE-2026-123892 (Important, 7.2), and CVE-2026-123893 (Moderate, 6.7). Reported by Arnoldas Radisauskas of NATO NCSC. |
| SDDC fixed versions | 9.1.1.0200 for 9.1.x.x; 9.0.2.0100 for 9.0.x.x; 5.2.5 for 5.x. Do not confuse 9.0.2.0100 with vCenter 9.0.2.0200. |
| CVE-2026-123894 | VMware Tools for Windows SAML token signature bypass, Moderate, CVSSv3 6.7. Reported by Noam Pomerantz. Fixed in 13.1.5.0 for 13.x and in 12.5.5 for the 12.3.x matrix row; the Q&A also mentions 11.x as fixed by 12.5.5. |
| Not listed as affected | ESX/ESXi, NSX, VCF Operations, VCF Automation, Workstation, and Fusion. This is not a VM escape. |
| Exploitation claims | The official VMSA does not state that the issues are being exploited in the wild. This article does not add that claim. |
FAQ
What is VMSA-2026-0009?
It is a Critical Broadcom security advisory, issued on November 19, 2026, for VMware vCenter, VMware Tools, and SDDC Manager. It addresses five privately reported vulnerabilities, CVE-2026-123890 through CVE-2026-123894. The support page header was last updated on November 20, 2026, and the status is OPEN. Official workarounds are none.
Which products are affected?
The VMSA lists VMware vCenter, VMware Cloud Foundation, VMware vSphere Foundation, VMware Tools, VMware Telco Cloud Platform, and VMware Telco Cloud Infrastructure. Use the official Response Matrix for the versions that are fixed. The Q&A says ESX/ESXi, NSX, VCF Operations, VCF Automation, Workstation, and Fusion are not affected by this advisory, though Windows VMs on Workstation or Fusion may still need a fixed Tools build if they could move into VCF or VVF.
What is CVE-2026-123890, and is it being exploited in the wild?
It is a Critical authentication bypass in the VMware Directory Service on vCenter, with a maximum CVSSv3 base score of 9.8. Official wording is that a malicious actor with network access to vCenter may bypass authentication and gain unauthorized access to the system. Mandiant reported the issue. The official advisory does not say it is being exploited in the wild, and this article does not claim that.
Which vCenter version should I install?
Install the fixed version that matches your branch in the official matrix: 9.1.1.0200 for 9.1.x.x, 9.0.2.0200 for 9.0.x.x, 8.0 U3m for vCenter 8.0, or 5.2.5 for VCF 5.x via KB 88287. For vCenter 7.0, contact Broadcom Support if you have an extended support contract; the advisory does not list a 7.0 patch version. Telco products should follow KB 463116.
What is the fixed SDDC Manager version for the 9.0 branch?
9.0.2.0100. That is the SDDC Manager and VCF Installer build for 9.0.x.x. It is not the same as vCenter 9.0.2.0200. On the 9.1 branch, the latest listed build that contains all three SDDC Manager fixes is 9.1.1.0200. VCF 5.x should update SDDC Manager to 5.2.5.
Are there official workarounds?
No. Each CVE section in the VMSA lists workarounds as none. The Q&A puts it as “not as listed by Broadcom.” Compensating controls, including firewalls, are an organization’s own decision. Stopping or uninstalling VMware Tools, or disabling guest operations, is not a workaround for CVE-2026-123894.
Does this affect ESXi, NSX, or Workstation?
The official Q&A says ESX/ESXi, NSX, Workstation, and Fusion are not affected by this VMSA. Windows guests on Workstation or Fusion may still need a fixed VMware Tools version if those VMs could be moved into a VCF or VVF environment.
Is vSphere 7.0 patched, and is this a VM escape?
vSphere 7.0 is impacted, and it reached End of General Support on October 2, 2025. If you have an active extended support contract, use those processes to request patches. The advisory does not publish a 7.0 fixed build. This is not a VM escape: the Q&A says none of the issues permit code execution on an ESX host from a virtual machine.
