What happened
Broadcom, which owns VMware, published security advisory VMSA-2026-0009 on November 19, 2026, and updated it on November 20, 2026. The most serious issue it fixes is CVE-2026-123890 in VMware vCenter, the central console used to manage VMware vSphere virtualization. The bug sits in the VMware Directory Service and allows an attacker to bypass authentication.
The flaw was reported to Broadcom by the security firm Mandiant. According to The Hacker News, citing Google Threat Intelligence Group and Mandiant, the suspected China-nexus group Armory Castle (formerly UNC5221) exploited it as a zero-day as early as September 2026, long before a patch existed.
Broadcom’s advisory does not mention exploitation, and as of this writing the flaw is not listed in the CISA KEV catalog. The same advisory also fixes four less severe bugs in SDDC Manager and VMware Tools for Windows. This article focuses mainly on the vCenter flaw.
Why it is dangerous
This is an authentication bypass, classified as CWE-288, meaning a way around the login through an alternate path. Picture a building where a guard checks badges at the main entrance, but a side service door has a broken lock and leads straight into the director’s office. The attacker needs no password, only a way to reach that door.
According to Broadcom, an attacker only needs network access to vCenter. No login and no user interaction are required. Google and Mandiant say a successful attack creates an authenticated session as [email protected], the main administrator account. According to The Hacker News, an attacker can then run commands and take files, including the directory service database.
vCenter controls every virtual server in the company, so whoever takes it over controls the whole virtualized infrastructure. According to The Hacker News, the attackers also deployed a tool that enables “Golden SAML” attacks, meaning forged authentication tokens. With it they could bypass multi-factor authentication and impersonate any user.
The CVSS score is 9.8 out of 10 under CVSS 3.1, assigned by the vendor, Broadcom (VMware). CVSS is an international severity scale, and anything from 9 up is rated critical. The CISA KEV catalog is a list kept by the US agency CISA of flaws with confirmed exploitation. This flaw is not in it yet, even though Google reports attacks.
Who is affected
According to Broadcom’s advisory, these versions are affected:
- vCenter 9.1.x.x and 9.0.x.x in VMware Cloud Foundation and VMware vSphere Foundation
- standalone VMware vCenter 8.0 and 7.0
- vCenter in VMware Cloud Foundation 5.x
- VMware Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 and VMware Telco Cloud Infrastructure 3.0
vCenter usually runs as a virtual appliance (vCenter Server Appliance) in a company server room or data center and manages ESXi hosts. The attack Google describes came from inside the network. According to The Hacker News, the attackers first broke into a BeyondTrust Remote Support device through a different flaw and then moved through other systems on the network to vCenter. If you do not use VMware vCenter or products that include it, this flaw does not affect you.
How to check if you are affected
In the vSphere Client, select the vCenter server in the inventory and look at the Summary tab, or open the Help menu and choose About. You can also find the version and build in the appliance management interface (VAMI) at https://<vcenter>:5480 on the Summary page.
If you have shell access to the vCenter Server Appliance, this read-only command prints the version:
vpxd -v
In PowerCLI you can check the version and build like this:
Connect-VIServer vcenter.company.local
$global:DefaultVIServers | Select-Object Name, Version, Build
These commands show the version and build number, not a label like U3m, so compare the build with the release notes of the fixed version. If your version is lower than the fixed version for your branch (see the fix section), you are vulnerable. Check every vCenter instance, including test environments.
How to fix it
Fixed versions according to Broadcom:
- vCenter 9.1.x.x (Cloud Foundation, vSphere Foundation): 9.1.1.0200
- vCenter 9.0.x.x (Cloud Foundation, vSphere Foundation): 9.0.2.0200
- vCenter 8.0: 8.0 U3m
- VMware Cloud Foundation 5.x: 5.2.5, see the async patching guide KB88287
- Telco Cloud Platform and Telco Cloud Infrastructure: see KB463116
- vCenter 7.0: fix only for customers with extended support, contact Broadcom Support
Broadcom states that there is no workaround. Updating is the only real protection.
Recommended steps:
- List every vCenter server in your organization and its version.
- Before updating, take a backup or snapshot of the vCenter Server Appliance as described in VMware documentation.
- Update first the vCenter that the most systems on your network can reach, then the rest.
- If you use SDDC Manager, update it too. The advisory fixes CVE-2026-123891 (CVSS 8.1), CVE-2026-123892 (7.2) and CVE-2026-123893 (6.7) there, with fixed versions 9.1.1.0200, 9.0.2.0100 and 5.2.5.
- If you run vCenter 7.0 without extended support, plan a move to a supported version as soon as possible.
Until the update is in place, restrict network access to vCenter to administrator machines only as a general precaution, for example with a firewall or a separate management network. The vendor does not list this as a substitute for patching, but it makes an attack harder. According to Google, the attackers scanned networks for open ports 9080, 5480 and 2012.
What if you may already be compromised
If your vCenter was reachable from other systems on your network, especially if you use BeyondTrust Remote Support, look for the traces from the Google and Mandiant analysis as reported by The Hacker News:
- unknown administrator accounts in the vsphere.local domain, Google mentions one starting with sps- (vSphere Client, Administration, Single Sign On, Users and Groups)
- SSH enabled on vCenter without your knowledge (VAMI, Access section), and PUT requests to
/rest/appliance/access/sshin the logs - an unknown process listening on TCP port 33992 on Linux appliances in your network
- suspicious JSP files on appliances and unexpected server traffic to Slack
- internal scanning of ports 9080, 5480 and 2012
You can search the vCenter Server Appliance logs, including older compressed ones, for requests that enabled SSH. The command only reads:
find /var/log/vmware -type f -exec zgrep -H "/rest/appliance/access/ssh" {} + 2>/dev/null
On Linux appliances in your network, check whether anything is listening on TCP port 33992:
ss -tlnp | grep 33992
An empty result does not prove that no attack happened. If you find any of these, bring in an incident response specialist. Patching alone is not enough in that case, because the attacker may have obtained data that lets them forge logins even after the fix.