VMware vCenter:a login bypass used as a zero-day since September. Patch now
Published
CVE-2026-123890 lets an attacker who can reach vCenter on the network skip the login and act as administrator. Mandiant says a suspected China-linked group used it from early September. Broadcom fixed it on 19 November and lists no workaround.
If you run VMware vSphere, update vCenter, the console that manages your ESXi hosts and virtual machines, today. On 19 November Broadcom published VMSA-2026-0009. Its headline flaw, CVE-2026-123890, lets an attacker with network access to vCenter bypass authentication. Broadcom rates it 9.8 out of 10 and lists no workaround (Broadcom).
Mandiant, which reported the flaw, says a suspected China-linked espionage group it calls ARMORY CASTLE exploited it in early September, more than two months before the fix (Mandiant).
Who is affected
- vCenter 9.1.x (fixed in 9.1.1.0200), 9.0.x (9.0.2.0200) and 8.0 (8.0 U3m). VMware Cloud Foundation 5.x gets vCenter 5.2.5 (Broadcom).
- vCenter 7.0 is affected too. Broadcom only offers a fix to customers with an extended support contract (Broadcom). Mandiant says the attack tool works against 7.x and 8.x (Mandiant).
- Patching for July's vCenter flaw doesn't help. CVE-2026-123890 is a different bug from CVE-2026-59309 in VMSA-2026-0006. Mandiant says the attackers used it in September against a vCenter that already had the July fix (Mandiant).
- The same advisory fixes three flaws in SDDC Manager (CVE-2026-123891, -123892 and -123893, rated 8.1, 7.2 and 6.7, all needing a login), used in VMware Cloud Foundation. It also fixes CVE-2026-123894 (6.7) in VMware Tools for Windows, which lets a privileged process inside a Windows virtual machine raise its rights there (Broadcom).
What has been seen so far
A snapshot from 20 November:
- Mandiant says the attackers first broke in through a zero-day in BeyondTrust Remote Support (CVE-2026-102764). They moved to an internal Linux server, scanned for VMware ports 9080, 5480 and 2012, then used a tool called BONESAW against vCenter's port 2012 (Mandiant).
- With it they created a single sign-on administrator account, copied vCenter's directory database and took its SAML signing key. A second tool used that key to forge logins, which Mandiant says lets them bypass multi-factor authentication and impersonate any user. They then turned on SSH and reached the ESXi hosts (Mandiant).
- CISA had not added it to its Known Exploited Vulnerabilities catalog. Its assessment in the CVE record, dated 19 November, still says exploitation “none”. Broadcom's advisory does not mention exploitation.
- We found no verified public exploit code. CIRCL's Vulnerability-Lookup tags two sightings as proof of concept: Mandiant's report and a Telegram post we could not verify.
What to do
- Update vCenter to 9.1.1.0200, 9.0.2.0200, 8.0 U3m or 5.2.5 for Cloud Foundation 5.x. Patches are cumulative, so later versions are also fixed (Broadcom FAQ). On 7.0 without extended support there is no fix: plan the move to 8.0 or 9.x now.
- Update VMware Tools in Windows virtual machines to 13.1.5.0 or 12.5.5, and SDDC Manager if you use Cloud Foundation (Broadcom FAQ).
- Limit who can reach vCenter, from inside too. Here the attackers came from a compromised internal server. Allow vCenter's ports only from named admin machines. Mandiant warns the built-in appliance firewall can't restrict by port or filter outbound traffic, and suggests its VCSA hardening tool (Mandiant). Test changes before relying on them.
- Check for signs of attack: single sign-on admin accounts you don't recognise, SSH switched on in vCenter without a reason, and the indicators listed by Mandiant.
- Found something? Treat it as an incident, not just a patch job. Updating closes the hole, but the attackers in Mandiant's case took the key used to sign vCenter logins (Mandiant).
- Use BeyondTrust Remote Support? Check BT26-05 is installed: it was the way in for this group.
- If an IT provider runs your servers, ask which vCenter build you are on and whether VMSA-2026-0009 is installed.
How we can help
Not sure whether your vCenter is exposed? Get in touch.
Sources
- Broadcom VMSA-2026-0009.1
- Broadcom: VMSA-2026-0009 questions and answers
- Mandiant (Google Threat Intelligence): ARMORY CASTLE exploits vSphere
- Mandiant: VCSA hardening and logging tool
- CVE.org: CVE-2026-123890 (VMware)
- NIST NVD: CVE-2026-123890
- CIRCL Vulnerability-Lookup: CVE-2026-123890
- BeyondTrust: BT26-05
- CISA: Known Exploited Vulnerabilities catalog