On November 19, 2026, Broadcom published security advisory VMSA-2026-0009, addressing five vulnerabilities found in VMware vCenter, the management server for virtualized infrastructure, and other products. Besides vCenter, the advisory covers SDDC Manager and VMware Tools for Windows, and its overall severity is rated Critical. Broadcom has not provided any workarounds, so updating to the fixed versions is the main remedy.
The Five Flaws Span vCenter, SDDC Manager and VMware Tools
According to the supplemental Q&A Broadcom published, the five issues map to the following products.
| CVE | Product | Issue |
|---|---|---|
| CVE-2026-123890 | vCenter | Authentication bypass in the VMware Directory Service |
| CVE-2026-123891 | SDDC Manager | SQL injection |
| CVE-2026-123892 | SDDC Manager | Authenticated command injection |
| CVE-2026-123893 | SDDC Manager | Local privilege escalation |
| CVE-2026-123894 | VMware Tools for Windows | SAML token signature bypass (only in configurations using guest alias mapping) |
CVSS 3.1 base scores range from 6.7 to 9.8. The vCenter authentication bypass is the kind of flaw an attacker who can reach vCenter over the network can target. The Q&A says the issues were reported by specific security researchers. Broadcom does not say in the Q&A whether any of them have been exploited.
No Workarounds, and Stopping VMware Tools Does Not Help
Broadcom lists no workarounds for these vulnerabilities. For the VMware Tools flaw, it says disabling guest operations does not protect against it, and stopping or uninstalling VMware Tools is not a workaround either. In short, applying the fixed versions is the only reliable option.
Affected products include standalone vCenter as well as vCenter deployed in VMware Cloud Foundation (VCF), VMware vSphere Foundation and Telco configurations. VMware Tools for Windows 13.x, 12.x and 11.x are affected. vSphere 7.0, which has reached the end of general support, is also affected, and Broadcom says the advisory has been updated accordingly. For the older vSphere 6.5 and 6.7, its position is that customers should "Presume that it does" apply. ESX, NSX, VCF Operations, VCF Automation, VMware Workstation and VMware Fusion are not affected.
Fixed Versions Include vCenter 8.0 U3m
The main fixed versions listed in the Q&A are as follows.
| Product | Fixed version |
|---|---|
| vCenter 8.0 | 8.0 U3m |
| SDDC Manager 9.1.x | 9.1.1.0200 |
| SDDC Manager 9.0.x | 9.0.2.0100 |
| SDDC Manager 5.x | 5.2.5 |
| VMware Tools for Windows 13.x | 13.1.5.0 |
| VMware Tools for Windows 12.x / 11.x | 12.5.5 |
For VCF 5.x, customers apply vCenter 8.0 U3m and SDDC Manager 5.2.5 following the asynchronous patching procedure. The Q&A does not explicitly state the fixed builds for vCenter 9.1 and 9.0, so administrators need to check the response matrix in the advisory itself. Broadcom says the fixes are cumulative and also include those from VMSA-2026-0008. Updating VMware Tools does not require upgrading the virtual machine hardware version.
VMs Keep Running During Updates, but Management Pauses
Broadcom says virtual machine and container workloads continue to run while vCenter is updated. However, the vSphere Client and other management methods are briefly unavailable during the update. Data-at-rest encryption operations against a Standard KMS (key management server), such as new encryptions and key rotations, also cannot run while vCenter is offline. Because SDDC Manager does not run workloads, Broadcom says updating it does not disrupt operations.
The vCenter updates in this advisory are not eligible for vCenter Quick Patch, which allows faster patching. Broadcom also says vCenter 8.0 U3m and 9.0.2.0200 are in a "Back-in-Time" relationship that blocks upgrades to VCF 9.1.1. It suggests either waiting for VCF 9.1.2 or upgrading vCenter to 9.1.1 first.
Source: VMSA-2026-0009 Questions & Answers (official VMware GitHub)
Our Take
vCenter is the management server that ties together an entire virtualized environment, so an authentication bypass there would not be confined to a single server. With no workaround available, administrators appear to be limited to updating or isolating vCenter from untrusted networks. On the plus side, workloads keep running during the update, which makes scheduling easier. Still, the Back-in-Time constraint and the pause in KMS operations are real caveats, so reading the Q&A alongside the advisory itself before starting work seems the safest approach.
Summary
With VMSA-2026-0009, Broadcom fixed five vulnerabilities, including a vCenter authentication bypass. Organizations running vCenter, SDDC Manager or VMware Tools for Windows are affected, and with no workarounds, updating to fixed versions is required. As of this writing, details such as the fixed builds for vCenter 9.x need to be confirmed in the advisory's response matrix.