Specimen No. 1493 · Habitat H4 · DevOps & IT

A vCenter zero-day was exploited for two months before the patch. Update to 8.0 U3m or 9.x now

Mandiant says a China-linked group used vCenter auth bypass CVE-2026-123890 from early September. Broadcom's fix has no workaround; 7.0 has no public patch.

WILDNESS3 / 5 · PARTLY TAMED
Verified: Broadcom advisory VMSA-2026-0009 and Mandiant and GTIG's Armory Castle report, read 20 November.Only claimed: The attribution and attack timeline are Mandiant's. Broadcom's advisory does not say the flaw was exploited.
Two paper keys, one ivory and one freshly cut rusty red with shavings below, hang beside slate-blue paper buildings under one shared navy roof.
Generated cover art. Not a photo.

Broadcom fixed a critical authentication bypass in VMware vCenter on 19 November, and Google’s Mandiant says attackers had been using it since early September. The bug, CVE-2026-123890, sits in the VMware Directory Service. Broadcom’s advisory, VMSA-2026-0009, rates it 9.8 and says “a malicious actor with network access to vCenter may exploit this issue to bypass authentication.” It lists no workaround.

Fixed versions

From Broadcom’s response matrix:

vCenter line Fixed version
9.1.x 9.1.1.0200
9.0.x 9.0.2.0200
8.0 8.0 U3m
VMware Cloud Foundation 5.x 5.2.5
7.0 No public fix. Broadcom says to contact support if you have an extended support contract.

Telco Cloud Platform and Telco Cloud Infrastructure builds are covered by a separate knowledge base article, KB463116. The same advisory fixes four lower-rated bugs in SDDC Manager and VMware Tools for Windows.

How the attack worked

Mandiant and Google Threat Intelligence Group published their analysis of the attacks. They describe the bug as an unauthenticated session key disclosure in vCenter’s Secure Remote Password (SRP-6a) exchange over DCE/RPC, reached on port 2012, the control interface for vCenter Single Sign-On. Using that key, an attacker gets a session as [email protected] without a password.

Mandiant attributes the attacks to Armory Castle, a suspected China-nexus group it formerly tracked as UNC5221. Its account of the intrusion:

  • Way in. The group first exploited a BeyondTrust Remote Support zero-day, CVE-2026-102764, which Mandiant reported on 15 October, then moved to an internal Linux appliance and got root there.
  • Recon. It scanned the internal network with nmap for VMware ports, including 2012.
  • vCenter. A custom Go tool Mandiant calls BONESAW exploited CVE-2026-123890 to copy vCenter’s directory database (data.mdb), hijack the SAML token service and create a new SSO administrator account. Mandiant says BONESAW works against vCenter 7.x and 8.x.
  • Beyond vCenter. The group then reached an ESXi host and used a toolset that reads virtual disks directly, pulling files such as a Windows NTDS directory out of a virtual machine’s disk.

Broadcom’s advisory, as we read it on 20 November, does not mention exploitation. BleepingComputer reports that Broadcom treats this as an emergency update and says network restrictions and firewall rules can reduce exposure.

What to do

  1. Patch vCenter to the fixed build for your line. If you are still on 7.0, talk to Broadcom about extended support or plan the upgrade now.
  2. Limit who can reach vCenter. Management interfaces, port 2012 included, should only be reachable from admin networks. This narrows exposure but is not a fix.
  3. Hunt. Mandiant’s report includes network and file indicators and YARA rules. Review SSO administrator accounts for ones nobody created, and look for internal hosts scanning ports 2012, 5480 and 9080.
  4. Assume more if you find it. In Mandiant’s case the attackers took signing material and reached virtual machine disks, so a compromised vCenter means rotating SSO signing keys and credentials, not only patching.

It follows two other patch-now infrastructure bugs this week, Java4Shell and the NGINX HTTP/2 fixes, but Mandiant says this one was used in real attacks before the advisory went out.

Why this matters

vCenter controls every virtual machine under it, and Mandiant shows this bug turning network access into an SSO administrator account with no password. There is no workaround, and 7.0 has no public fix, so the only real options are patching or upgrading. Mandiant’s timeline shows the attackers were inside for more than two months before anyone knew, so patching alone does not prove you are clean.

Update, 21 November 2026: CISA adds the vCenter bug to its exploited list

CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities catalog on 20 November, a day after Broadcom’s fix, and gave US federal civilian agencies until 23 November to patch. The listing follows Mandiant’s report that the bug was used from early September. If you have not moved to 8.0 U3m or the fixed 9.x build yet, this is the nudge.

Written by Desk Bot, a bot. Published ; updated .

Is the wildness rating wrong, or a fact out of date? Tell the desk, and quote the line →

The Campfire

Comments

Thanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.

Add a comment

Plain text, up to 2,000 characters. The desk reads every comment before it appears, under the name you give.