Patch vCenter now: a login bypass has been exploited since September, and July's vCenter patch doesn't cover it
CVE-2026-123890 lets an attacker who can reach vCenter skip the login entirely. CISA lists it as exploited. Here is what to install, what to lock down, and what to check.
If you run VMware vCenter, the server that manages your ESX hosts, install Broadcom’s November update this week. On November 19, 2026, Broadcom published advisory VMSA-2026-0009 to fix CVE-2026-123890, an authentication bypass in vCenter rated 9.8 out of 10. The next day, the Cybersecurity and Infrastructure Security Agency (CISA) added it to its Known Exploited Vulnerabilities (KEV) catalog, with a federal due date of November 23.
The flaw is in the VMware Directory Service, the part of vCenter that handles single sign-on. Anyone who can reach vCenter over the network can get in without a password. There is no workaround. The update is the fix.
Who’s affected
Any vCenter older than the fixed versions below, whether you run it on its own or as part of VMware Cloud Foundation or vSphere Foundation.
This is a new flaw. If you installed the vCenter fixes from VMSA-2026-0006 over the summer (see our earlier VMware article), you still need this one. Broadcom’s FAQ says the two are separate issues, and that the new builds include the earlier fixes.
You don’t need to update your ESX hosts for this advisory. Broadcom says ESX is not affected.
It’s already being used
Broadcom’s advisory doesn’t say whether the flaw has been exploited. Google’s Mandiant team does. In a November 19 report, Mandiant and Google Threat Intelligence said a suspected China-linked espionage group it tracks as ARMORY CASTLE (formerly UNC5221) has used the flaw since early September 2026, more than two months before a patch existed.
In the case Mandiant described, the vCenter wasn’t on the internet. The attackers first got in through a different zero-day in BeyondTrust Remote Support, CVE-2026-102764, which we covered in October. From there they moved to other internal machines, found vCenter, and used this flaw to make themselves administrators. With that access they went on to the ESX hosts and the data stored on them.
The lesson for small shops: keeping vCenter off the internet is necessary, but it isn’t enough. Assume that any compromised machine on your network can reach your vCenter.
If you also run BeyondTrust Remote Support and it was unpatched for any length of time in September or October, treat this as a possible compromise, not just a patch job. Follow the hunting steps below, and consider bringing in incident response help.
What to install
From Broadcom’s advisory, as of November 20, 2026:
| You run | Install this or later |
|---|---|
| vCenter 9.1.x | 9.1.1.0200 |
| vCenter 9.0.x | 9.0.2.0200 |
| vCenter 8.0 | 8.0 U3m |
| VMware Cloud Foundation 5.x | 5.2.5 (vCenter 8.0 U3m through Broadcom’s asynchronous patching process, KB 88287) |
| vCenter 7.0 | No public fix. Contact Broadcom Support if you have an extended support contract |
Updates are cumulative, so any newer build also fixes this. On vSphere 8 you have to be on Update 3 to get the fix. Broadcom’s FAQ says vSphere 7 reached End of General Support on October 2, 2025. It also says versions 6.5 and 6.7 should be presumed affected, and they will never get a fix. If you’re on one of those versions without extended support, plan the upgrade or replacement now, and in the meantime lock down network access to vCenter as described below.
To check your version, look at the Summary tab in the vSphere Client, or the update page of the vCenter management interface (VAMI) on port 5480.
Notes before you start:
- Your virtual machines keep running. Updating vCenter takes the vSphere Client offline for a while, but the virtual machines on your hosts keep working. Broadcom’s FAQ also says that some encryption tasks, such as creating new encrypted VMs or rotating keys, won’t work while vCenter is down.
- Back up vCenter first. Use the file-based backup in the VAMI, or take a snapshot of the vCenter VM if your setup allows it.
- Mid-upgrade? Broadcom warns that vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1 until 9.1.2 comes out. If you’re partway through a 9.1 upgrade, read question 39 of the FAQ before you patch.
- Engineered systems (VxRail, SimpliVity and similar) get their patches from that vendor. Ask them.
The rest of the advisory
The same advisory fixes two other things:
- VMware Tools for Windows (CVE-2026-123894, rated 6.7): someone who already has admin-level access inside a Windows VM could gain more rights in that VM. Update Tools in your Windows guests to 13.1.5.0, or to 12.5.5 if you’re on 12.x or 11.x. You don’t need to change the VM hardware version.
- SDDC Manager (three flaws): this only matters if you run VMware Cloud Foundation. The fixed versions are listed in the advisory.
Lock down who can reach vCenter
Patching closes this hole. Restricting network access helps against the next one:
- Only the admin workstations or jump box you use for vSphere should be able to reach vCenter’s web interface (443), the management interface (5480), and SSH (22). Servers, desktops, and appliances shouldn’t. Mandiant also calls out TCP 2012, the single sign-on control port used in these attacks.
- Enforce this on a firewall or VLAN boundary. Don’t rely on the VAMI’s built-in firewall. Mandiant notes that it only filters incoming traffic, doesn’t log denied connections, and can be turned off by anyone with VAMI admin rights.
- Limit outbound traffic from vCenter and ESX hosts to what they actually need.
- Send vCenter and ESX logs to a syslog server or SIEM that the vSphere admins can’t wipe.
Check for signs someone was already in
If your vCenter was unpatched and reachable from more than a handful of trusted machines, look for these, based on Mandiant’s report:
- Single sign-on or local vCenter administrator accounts you didn’t create
- SSH turned on for vCenter when nobody on your team did it, or SSH turned on and then off again
[email protected]sign-ins at odd times or from unexpected addresses- New SSH keys for root on ESX hosts, or SSH logins to hosts that you can’t explain
- Outbound connections from vCenter, ESX, or Linux appliances to services they shouldn’t use (Mandiant saw Slack used for remote control)
If you find any of these, don’t just patch and move on. Disconnect carefully, preserve the logs, and get incident response help. Our first-hour guide covers the basics of what not to destroy.
If any of these systems hold or process criminal justice information (CJI) or bank customer data, confirm with your CJIS Systems Agency (CSA), examiner, or counsel whether a possible compromise has to be reported.
Sources
- Broadcom security advisory VMSA-2026-0009 (notification 39495): CVEs, severities, fixed versions, no workarounds, and VMware Tools versions
- VMSA-2026-0009 questions and answers (Broadcom, GitHub): ESX not affected, separate from CVE-2026-59309, vSphere 7 and 6.x status, effect on running VMs, and the VCF 9.1.1 upgrade restriction
- CISA Known Exploited Vulnerabilities catalog: CVE-2026-123890 added November 20, 2026, due November 23, 2026
- NVD entry for CVE-2026-123890: description, affected versions, and the CVSS 3.1 score of 9.8
- Google Threat Intelligence and Mandiant: ARMORY CASTLE exploits vSphere: exploitation since early September 2026, the BeyondTrust entry point, and the hardening and hunting guidance
From Small Town Sysadmin
Get new guides by email
Plain-English tech tips, scam and security alerts, and fixes for small offices, whether you're the office manager or the IT pro. No spam, and you can unsubscribe anytime.