All CVEs

VMware vCenter CVE-2026-123890 (VMSA-2026-0009): unauthenticated attackers with network access to vCenter get an administrator session (9.8). Exploited in early September by a suspected China-nexus group (Mandiant: ARMORY CASTLE), on CISA KEV since 20 Nov (due 23 Nov). No workaround. Fix: 9.1.1.0200, 9.0.2.0200 or 8.0 U3m (VCF 5.x: vCenter 8.0 U3m or VCF 5.2.5); no public fix for 7.0. Also allowlist ports 443/2012 and look for rogue SSO admin accounts. https://tldrcve.com/vcenter-zero-day/

VMware vCenter · CVE-2026-123890

vCenter zero-day

Patch nowExploited in the wild, on KEV. No workaround.

A bug in VMware vCenter's directory service lets anyone who can reach vCenter over the network get an administrator session without a password. Mandiant says a suspected China-nexus group, ARMORY CASTLE, exploited it in early September to create a rogue admin account and steal vCenter's login-signing key, and CISA added it to its exploited list on 20 Nov 2026. Broadcom fixed it on 19 Nov and gives no workaround; for vCenter 7.0 it lists no public fix and tells extended-support customers to contact Broadcom Support.

How scary is it?

updated 22 Nov
  • Yes: Works without logging in1,4
  • Partly: Shown working, code not public2
  • Yes: Attacks seen in the wild2,3
  • Yes: On CISA's exploited list (fix by 23 Nov)3

Scare-o-meter

Drop everything

Attackers are already on it.
Patch now.

Are you affected? only if all are true

1vCenter before the fix

Below 9.1.1.0200, 9.0.2.0200 or 8.0 U3m. On VMware Cloud Foundation 5.x, you're affected until vCenter is on 8.0 U3m, which VCF 5.2.5 includes (for Telco Cloud, see Broadcom KB463116). vCenter 7.0 is affected too, and Mandiant says the attackers' tool works on 7.x and 8.x; Broadcom says to presume 6.5 and 6.7 are affected. The bug is in vCenter's directory service; Broadcom's FAQ says ESX isn't affected.1,2,4,5

2An attacker can reach vCenter

Network access to vCenter is enough; no login is needed. In the attack Mandiant investigated, the attackers first broke into another machine on the internal network, then reached vCenter's single sign-on port 2012 from there.1,2

What to do

1Patch now

Install 9.1.1.0200, 9.0.2.0200 or 8.0 U3m (on VCF 5.x, patch vCenter to 8.0 U3m or move to VCF 5.2.5); Broadcom's patches are cumulative, so later versions also fix it. Broadcom gives no workaround. CISA's deadline for US agencies is 23 Nov 2026. Heads-up from Broadcom: 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1, so patch now and wait for 9.1.2 before that upgrade (or move vCenter to 9.1.1 first and patch there). The same advisory also covers four lesser bugs that need an account or local access, in SDDC Manager and VMware Tools for Windows (CVE-2026-123891 to CVE-2026-123894), with their own fixed versions.1,3,5

Latest safe versions checked 22 Nov

VMware vCenter → 9.19.1.1.02009.09.0.2.02008.08.0 U3mVMware Cloud Foundation 5.x: patch vCenter to 8.0 U3m, or move to VCF 5.2.5, which includes it.
2On vCenter 7.0?

Broadcom lists no public fix for 7.0 and tells customers with an extended support contract to contact Broadcom Support to request patches. Without one, there is no fix for 7.0.1,5

3Limit who can reach vCenter

Mandiant recommends a default-deny firewall on vCenter that allows its management ports, including 443 and 2012, only from an allowlist of trusted hosts. In its write-up, allowlisting port 2012 would have stopped the exploit, and allowlisting 443 would have stopped the attackers using the logins they forged. This adds protection; it doesn't replace the patch.2

4Check for a break-in

Patching doesn't remove attackers who are already in, and CISA flags this one for forensic triage. Look for single sign-on administrator accounts you didn't create, and for Mandiant's file indicators, such as /tmp/123, /tmp/sss, /tmp/dbr and /usr/bin/vmtoolscs, on other internal Linux machines the attackers took over. The attackers also took vCenter's SAML signing key, which lets them forge logins for any user.2,3

This page shows you how to check. It can't tell you you're safe.

Sources (5) and changelog
  1. Broadcom VMSA-2026-0009 (updated as .1 on 20 Nov): affected and fixed versions, no workaround, 7.0 19 Nov
  2. Mandiant / Google: ARMORY CASTLE exploited it in early September, port 2012, indicators, hardening 20 Nov
  3. CISA KEV catalog: CVE-2026-123890 added 20 Nov, due 23 Nov
  4. CVE record: CVE-2026-123890, CVSS 9.8, no login, CISA: exploitation active 19 Nov
  5. Broadcom: VMSA-2026-0009 FAQ, patches are cumulative