A critical vCenter vulnerability, CVE-2026-123890, lets an attacker who can reach vCenter on the network skip the login and act as an administrator. Broadcom published the fix in VMSA-2026-0009 on November 19, 2026, rated it CVSS 9.8, and lists no workaround. Google’s Mandiant team, which reported the flaw, says a suspected China-nexus group used it in an intrusion in early September.
vCenter is the server that manages VMware ESX hosts and every virtual machine on them. Whoever controls vCenter controls the file servers, domain controllers and databases that run as VMs. Many small organizations have one vCenter on a few on-site hosts, set up years ago and now looked after by an MSP. This post covers what the flaw is, which builds fix it, what to do if you are still on vCenter 7, what the attackers did, and what to ask your MSP. Facts are as of November 20, 2026.
The short version: find out what vCenter version you run. If it is 8.0, install 8.0 U3m now. If it is part of VMware Cloud Foundation or vSphere Foundation, install the fixed build in the table below. If it is 7.0 or older, there is no public patch. Cut network access to vCenter down to the admins who need it and plan the upgrade.
What the vCenter vulnerability is
Broadcom’s advisory describes CVE-2026-123890 as an authentication bypass in the VMware Directory Service, the part of vCenter that handles single sign-on. "A malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system," the advisory says. It rates the vCenter vulnerability Critical with a CVSS score of 9.8. Our guide to reading a CVSS score explains why a network attack with no login scores that high.
Broadcom’s supplemental FAQ says the vCenter issue qualifies as an emergency change. It also says that if you are not sure whether a system is affected, "presume it is vulnerable."
Google Threat Intelligence Group’s November 19 report gives the technical detail. The flaw leaks a session key over the directory service’s remote procedure call interface on TCP port 2012. With that key, an attacker gets a session as administrator@vsphere.local, the built-in top account. Google says the attack tool works against vCenter 7.x and 8.x appliances.
What else VMSA-2026-0009 fixes
The advisory covers five CVEs. The other four matter less to most small organizations:
- SDDC Manager, CVE-2026-123891, -123892 and -123893. An SQL injection, a command injection and a local privilege escalation. All need an attacker who is already logged in. SDDC Manager is part of VMware Cloud Foundation (VCF), so most small shops do not run it.
- VMware Tools for Windows, CVE-2026-123894. A SAML token signature bypass that lets a privileged process inside a Windows VM raise its rights in that VM. It only works on VMs set up with guest alias mapping. Fixed in VMware Tools 13.1.5.0 and 12.5.5.
Broadcom’s FAQ says ESX itself is not affected, and neither are NSX, VCF Operations, VCF Automation, Workstation or Fusion. It also says none of these flaws let a VM break out and run code on the ESX host. Broadcom updated the advisory on November 20 to clarify which VMware Tools versions are affected.
Which vCenter builds fix it
Here are the fixed builds for the vCenter vulnerability from Broadcom’s response matrix:
| What you run | Fixed build | Notes |
|---|---|---|
| vCenter 8.0 | 8.0 U3m | Most standalone vSphere 8 shops |
| VCF or VVF 9.1.x | vCenter 9.1.1.0200 | SDDC Manager 9.1.1.0200 too |
| VCF or VVF 9.0.x | vCenter 9.0.2.0200 | SDDC Manager 9.0.2.0100 |
| VCF 5.x | vCenter 8.0 U3m and SDDC Manager 5.2.5 | Use the async patching guide, KB 88287 |
| vCenter 7.0 | No public fix | Contact Broadcom if you have extended support |
Some practical points from Broadcom’s FAQ:
- You can check the build on the Summary tab in the vSphere Client.
- The update can be applied through the usual vCenter appliance management interface (VAMI). It is not eligible for vCenter Quick Patch.
- Updating vCenter does not stop running VMs. Some encryption tasks that depend on a key server are unavailable while vCenter is offline.
- Patches are cumulative, so you do not need to install earlier VMSA fixes first.
- Confirm the new vCenter supports the ESX versions you run before you update.
There is one known issue. Broadcom says vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1, which it calls a "Back-in-Time" issue. It expects a fix in VCF 9.1.2. If you are partway through a VCF 9.1 upgrade, read the FAQ before you patch.
If you run a packaged system such as Dell VxRail or HPE SimpliVity, Broadcom says to follow that vendor’s guidance for the update.
If you are still on vCenter 7
This is the hard part for many small organizations. Broadcom lists no public fix for the vCenter vulnerability on vCenter 7.0. Its FAQ says vSphere 7 reached end of general support on October 2, 2025. Broadcom does not evaluate products past that date, so it tells customers to presume vCenter 7 is affected. The same goes for vSphere 6.5 and 6.7. Google’s report confirms the attack tool works on 7.x.
Your options:
- Extended support. If you bought it, request the patch through that process, per Broadcom.
- Upgrade. Broadcom points customers to VCF 9.1. Moving to vCenter 8.0 U3m is the other supported path, if your hosts and license allow it.
- Cut access now. Broadcom lists no workaround. Its FAQ does say perimeter and appliance firewall settings may serve as compensating controls, and that each organization must decide whether to rely on them.
Our post on Windows Server 2016 end of support walks through the same "upgrade, move, pay or retire" choice for another server platform.
What the attackers did with the vCenter vulnerability
Google tracks the group as ARMORY CASTLE, formerly UNC5221, a suspected China-nexus espionage actor. Its report says the group first broke into a BeyondTrust Remote Support appliance through a different zero-day. From there, it moved to an internal Linux appliance with no endpoint protection and scanned for VMware ports, including 443, 2012 and 5480.
According to Google, the group then:
- Ran a tool Google calls BONESAW against vCenter to create a new single sign-on admin account.
- Stole the vCenter directory database and the key used to sign login tokens, which let it forge logins.
- Turned on SSH through the appliance management API, took the vCenter master key and database passwords, then turned SSH off again.
- Logged in to ESX hosts as root and copied Windows domain controller files straight off VM disks.
Google says the tool’s build date points to July 2026, which suggests it was made for wider use. Google urges immediate patching and says patching alone is not enough to protect vCenter. Broadcom’s own advisory does not mention exploitation; it thanks Mandiant for the report.
As of the morning of November 20, CISA had not added CVE-2026-123890 to its KEV catalog. Our KEV explainer covers what a listing means. Do not wait for one before you patch this vCenter vulnerability.
How to check whether the vCenter vulnerability was used
Google’s report lists file names to look for on vCenter and nearby Linux systems. These include /tmp/123, /tmp/sss, /tmp/dbr and /usr/bin/vmtoolscs, plus web shells named ActiveSer.jsp and u.jsp. The report also includes YARA rules and a list of network addresses.
Other signs worth checking:
- Single sign-on admin accounts in vsphere.local that nobody on your team created.
- SSH turned on for the vCenter appliance when you did not turn it on.
- Unknown keys in the root account’s authorized keys on ESX hosts.
- Connections to vCenter on port 2012, the port Google says the attack uses, from machines that have no reason to talk to it.
Google also recommends tighter firewall rules on the vCenter appliance itself, with a default-deny posture and only named admin systems allowed in. It points to Mandiant’s VCSA hardening tool for this, and advises testing any such rules carefully first. The same lesson showed up in our post on the Check Point Gaia vulnerability, where attackers reached ESXi hosts from a breached firewall.
What to ask your MSP about the vCenter vulnerability
If an MSP runs your VMware hosts, you may never log in to vCenter yourself. Ask in writing:
- What vCenter version and build do we run? Compare it to the table above.
- When will 8.0 U3m or the right VCF build be installed? Broadcom treats this as an emergency change.
- If we are on vCenter 7, what is the plan and date to upgrade? Ask what it will cost.
- Which systems can reach vCenter on the network? It should be a short list of admin machines.
- Did you check for unknown SSO admin accounts and the files Google lists? Ask what they found.
Our posts on the MSP Process breach and the ScreenConnect attack cover more questions to ask a provider this month.
Frequently Asked Questions
What is CVE-2026-123890?
A vCenter vulnerability in the VMware Directory Service that lets an attacker with network access bypass login and act as administrator. Broadcom rates it CVSS 9.8, Critical.
Is it being exploited?
Google’s Threat Intelligence Group and Mandiant say a suspected China-nexus group used it in early September 2026. Broadcom’s advisory does not state exploitation.
Is it in CISA’s KEV catalog?
Not as of the morning of November 20, 2026. Patch now anyway.
Which build fixes vCenter 8?
vCenter 8.0 U3m. VCF and VVF 9.1.x need 9.1.1.0200, and 9.0.x needs 9.0.2.0200.
Is there a patch for vCenter 7?
No public one. Broadcom says to presume vCenter 7 is affected and to use extended support if you have it, or upgrade.
Is there a workaround?
Broadcom lists none. Its FAQ says firewall settings may act as compensating controls, and each organization must decide whether to rely on them.
Do I need to patch my ESX hosts?
Not for this advisory. Broadcom says ESX is not affected. Check that the new vCenter build supports your ESX version.
Will patching vCenter take my VMs down?
No. Broadcom says running workloads keep running while vCenter updates. Some key server tasks pause while vCenter is offline.
What about VMware Tools?
Windows VMs need VMware Tools 13.1.5.0 or 12.5.5 for a separate, lower-rated flaw. It only matters on VMs that use guest alias mapping.