Skip to content

VMware vCenter CVE-2026-123890: Exploited Zero-Day, How to Check, Patch and Spot a Break-In

ID badge on a red lanyard reading ALL ACCESS, administrator@vsphere.local, password not required, stamped zero-day

On November 19, Broadcom shipped emergency fixes for CVE-2026-123890, a flaw in VMware vCenter that lets an attacker walk straight in as the top administrator. No password. No login prompt. Just network access to the server.

That alone would earn a 9.8 out of 10. What makes it worse is the timing. Google's Mandiant team says a suspected Chinese espionage group was already using the bug since at least early September, more than two months before anyone outside could patch it. A day after the fix, CISA added it to its list of vulnerabilities that attackers are actively exploiting.

vCenter is the control room for a VMware setup. Whoever controls it can reach every virtual machine it manages. So this guide covers three things in plain English: how to tell whether your vCenter is affected, which version fixes it, and how to check whether someone got in before you patched.

Last checked: November 22, 2026.

The short version

What it is An authentication bypass in vCenter's VMware Directory Service that hands an attacker an administrator session
Severity 9.8 out of 10 (CVSS 3.1), rated Critical by Broadcom
Attacked yet? Yes. Exploited as a zero-day since at least early September 2026, and on CISA's exploited list since November 20
Affected vCenter 7.0, 8.0, 9.0 and 9.1 before the fixed builds, including vCenter inside VMware Cloud Foundation (VCF) and vSphere Foundation
Fixed in vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m. VCF 5.x: 5.2.5
vCenter 7.0 No public fix. It left general support in October 2025
Workaround None
Not affected ESX hosts themselves, NSX, VCF Operations, VCF Automation, Workstation and Fusion

What is CVE-2026-123890, in plain English?

Every vCenter server runs a built-in directory service. It's the part that keeps track of users, passwords and the keys that sign login tokens. Other parts of vCenter talk to it over a private channel on TCP port 2012.

When something logs in through that channel, the two sides agree on a secret session key. Google found that this key isn't as secret as it should be. Part of it comes from a timestamp that an attacker can predict. Work out the timestamp and you can work out the key, without ever knowing a password.

With that key, the attacker gets a session as [email protected], the built-in super-admin account. From there they can run commands and copy files off the server, including the directory database that holds everyone's login secrets.

Broadcom credits Mandiant with finding the bug. Its advisory, VMSA-2026-0009, describes it simply as an authentication bypass in the VMware Directory Service.

Quick poll

Do you look after a VMware vCenter server?

Tap an answer to see how other readers voted.

How the attackers used it

Google's threat team published the full story of the break-ins on November 20. It reads like a heist in slow motion. The group, which Google tracks as Armory Castle (formerly UNC5221), followed these steps:

  1. Got inside the network first. They broke in through a different zero-day, in BeyondTrust Remote Support (CVE-2026-102764). So the vCenter bug wasn't their front door. It was the key to the vault once they were in.
  2. Hid on a quiet Linux box. They planted web shells on an internal appliance with no security software watching it.
  3. Took over vCenter. A custom tool Google calls BONESAW used CVE-2026-123890 to create a new single sign-on admin account and copy the directory database.
  4. Forged logins. With the stolen signing keys, they could create their own login tokens. Google says this let them "bypass MFA, and impersonate any user."
  5. Reached the hosts and the data. They added their own SSH key to the root account on an ESXi host, then pulled Active Directory password data straight off a Windows virtual machine's disk.
  6. Stayed in. They left backdoors behind, including one that took orders through Slack.

One detail matters for anyone who patched in the summer. A different vCenter login bug, CVE-2026-59309, was made public on July 29. Google's logs show Armory Castle used the new bug against a vCenter server that was already patched for the July one. Broadcom confirms the two are separate flaws. If you patched in July, you still need this update.

Am I affected? Check your vCenter version

You're exposed if you run vCenter 7.0, 8.0, 9.0 or 9.1 on any build older than the fixed ones below. That includes the vCenter built into VMware Cloud Foundation, vSphere Foundation and Broadcom's Telco Cloud platforms.

To see your version, use any of these:

  • vSphere Client: select your vCenter server in the inventory and open the Summary tab. It shows the version and build.
  • Appliance management page: open https://your-vcenter:5480, sign in and check the Summary page.
  • PowerCLI: after Connect-VIServer, run $global:DefaultVIServer.Build.

Then compare it with this table, from Broadcom's advisory:

You run Update to
vCenter 9.1.x (VCF or vSphere Foundation) 9.1.1.0200
vCenter 9.0.x (VCF or vSphere Foundation) 9.0.2.0200
vCenter 8.0 8.0 U3m
VCF 5.x 5.2.5 (patch vCenter on its own using Broadcom KB 88287)
Telco Cloud Platform or Telco Cloud Infrastructure Follow Broadcom KB 463116
vCenter 7.0 No public fix. Extended-support customers should ask Broadcom Support

Your ESXi hosts don't need this patch. Broadcom says ESX isn't affected, and none of the bugs in this advisory let a virtual machine break out onto its host.

How to patch vCenter

Broadcom calls this an emergency change, so you can skip the usual monthly patch window. Here's the order that keeps things calm:

  1. Back up first. Take a file-based backup of the vCenter appliance from the management page on port 5480. A snapshot of the vCenter VM is a handy extra.
  2. Use the full update, not Quick Patch. Rapid7 notes this fix can't be applied with vCenter's Quick Patch feature. Use the normal update process for your version: the appliance management page for standalone vCenter, or SDDC Manager on VCF.
  3. Expect a short outage of vCenter itself, not your VMs. Broadcom says running workloads keep going while vCenter updates. You just lose the management console for a while.
  4. Check the build afterwards. Look at the Summary tab again and make sure it shows the fixed build.

One catch for VCF 9 upgrades. Broadcom warns that vCenter 8.0 U3m and 9.0.2.0200 block a later move to VCF 9.1.1, which is older code. If you're halfway through that upgrade, check Broadcom's FAQ first. Broadcom suggests waiting briefly for VCF 9.1.2.

There's no workaround. Broadcom lists none. Limiting who can reach vCenter on the network is good practice and makes an attack harder, but it isn't a fix. Google's own example shows why: these attackers came from inside the network.

Still on vCenter 7.0?

You have a real problem. vSphere 7 left general support on October 2, 2025, and Broadcom hasn't published a public patch for 7.0. Mandiant told SecurityWeek that the attackers' tool works on 7.x as well as 8.x.

Your options:

  • Extended support contract? Open a case with Broadcom and ask for the CVE-2026-123890 patch.
  • No contract? Plan the move to 8.0 U3m or newer now. Until then, cut network access to vCenter down to a few admin machines, and watch it closely for the signs below.

How to check whether you were already hacked

Patching closes the door. It doesn't remove anyone who's already inside. Mandiant CTO Charles Carmakal put it plainly: "Organizations should both apply the patches and examine their systems for evidence of compromise." CISA is asking US agencies for the same kind of forensic check.

Google's report lists what to look for. Start with these:

  • Admin accounts you don't recognise. In the vSphere Client, go to Administration → Single Sign On → Users and Groups and review the Administrators group. The attackers created local accounts ending in @vsphere.local, with names starting sps-.
  • SSH switched on, then off again. They turned on the appliance's SSH through the management API (a PUT request to /rest/appliance/access/ssh), took what they needed, then turned it off. Look for this in your logs.
  • Odd files on the appliance. On the vCenter shell, check for files the report names, such as /tmp/123, /tmp/sss, /tmp/dbr and /usr/bin/vmtoolscs:
ls -la /tmp/123 /tmp/sss /tmp/dbr /usr/bin/vmtoolscs 2>/dev/null
  • Strange listening ports. One backdoor, run from /tmp/dbr, listened on TCP 53 and 33992. This command shows which program owns each of those ports:
ss -ltnp | grep -E ':(53|33992)\b'

A program running from /tmp is a red flag. Port 33992 has no business being open on vCenter at all.

  • SSH keys you didn't add on your ESXi hosts (root's keys live in /etc/ssh/keys-root/authorized_keys), and a hidden .a folder or o.tar.gz archive on your datastores.
  • Scans for ports 2012, 5480 and 9080 from inside your own network.

Finding nothing is a good sign, not a clean bill of health. Attackers rename their tools. If anything turns up, treat it as a full incident: the attackers may hold your signing keys and Active Directory data, so resetting one password won't be enough. Bring in an incident response team.

Quick poll

Where is your vCenter right now?

Tap an answer to see how other readers voted.

What else is in the same advisory?

VMSA-2026-0009 fixes four smaller bugs too. None has been reported as exploited, but they come in the same update cycle:

CVE Product What it does Score Fixed in
CVE-2026-123891 SDDC Manager SQL injection 8.1 9.1.1.0200, 9.0.2.0100, 5.2.5
CVE-2026-123892 SDDC Manager Command injection after login 7.2 Same as above
CVE-2026-123893 SDDC Manager Local escalation to root 6.7 Same as above
CVE-2026-123894 VMware Tools for Windows Bypass of SAML token signature checks 6.7 13.1.5.0, or 12.5.5 for 12.x

If you run VCF, update SDDC Manager as well. For Windows virtual machines, roll out the new VMware Tools on your normal schedule.

It's been a busy week for patches

This was one of several critical fixes in a single week. Web servers got nginx2root, and Java apps got Java4Shell. The lesson from vCenter is that the attackers didn't come in through vCenter. They came in through another product, then used vCenter to take everything. Locking down the rest of the network matters as much as patching any one box. Our new Linux server checklist covers the basics.

Quick answers

What is CVE-2026-123890? A critical authentication bypass in the VMware Directory Service inside vCenter Server. An attacker who can reach vCenter on the network can get an administrator session without a password. It's rated 9.8 (CVSS 3.1).

Is CVE-2026-123890 being exploited? Yes. Google's Mandiant says a suspected China-nexus espionage group, Armory Castle, has used it since at least early September 2026. CISA added it to its Known Exploited Vulnerabilities catalog on November 20, 2026.

Which vCenter version fixes it? vCenter 9.1.1.0200, 9.0.2.0200 or 8.0 U3m. VMware Cloud Foundation 5.x is fixed in 5.2.5.

Is vCenter 7.0 affected? Yes, and there's no public patch. vSphere 7 left general support in October 2025. Customers with extended support should ask Broadcom for the fix.

Is there a workaround? No. Broadcom lists none. Restricting network access to vCenter lowers the risk but doesn't fix the bug.

Do I need to patch my ESXi hosts? Not for this bug. ESX isn't affected. But check your hosts for SSH keys you didn't add, because the attackers moved from vCenter to ESXi.

Will patching vCenter stop my virtual machines? No. Broadcom says running workloads continue during the update. Only the vCenter management console goes offline for a while.

What port does CVE-2026-123890 use? Google's report says the attack goes through vCenter's single sign-on control channel on TCP port 2012.

Is there a public exploit? None had been reported as of November 20. The attackers used their own private tool. That can change quickly, so don't wait for one to appear.

I patched for the July vCenter bug. Am I safe? No. CVE-2026-59309, from July, is a separate flaw. Google saw this new bug used against a server already patched for the July one.

Check the build, apply the update, then look for the signs above. With this bug, a fast patch is only half the job.

Sources

The facts in this article were checked against these sources.

  1. Broadcom VMSA-2026-0009: VMware vCenter, SDDC Manager and VMware Tools updates support.broadcom.com
  2. Broadcom VMSA-2026-0009 questions and answers github.com
  3. Google Threat Intelligence: ARMORY CASTLE exploits vSphere cloud.google.com
  4. CISA Known Exploited Vulnerabilities catalog cisa.gov
  5. CISA adds four known exploited vulnerabilities to catalog (November 20, 2026) cisa.gov
  6. NVD: CVE-2026-123890 nvd.nist.gov
  7. Rapid7: CVE-2026-123890, critical authentication bypass in VMware vCenter rapid7.com
  8. SecurityWeek: newly patched VMware vCenter flaw exploited as zero-day securityweek.com
  9. Help Net Security: VMware vCenter zero-day exploited for months before patch helpnetsecurity.com
  10. Mandiant VCSA Hardening and Logging Tool github.com