Critical vCenter Zero-Day

Exploited Since September

Published 20 November 2026, 9 pages, Mitigata Threat Research

In plain words

Hackers found a secret way into the control room that runs many computers at once. They used it from September, and the fix only came out in November. Block that way in now, and look back to August for signs someone already got through.

For business leaders

A China-linked espionage group, ARMORY CASTLE, used a flaw in VMware vCenter from early September 2026, more than two months before a fix existed. Whoever controls vCenter controls every virtual machine it manages, so systems holding core operations, customer data and money are exposed. The source gives no cost figure. Confirm this week that every vCenter and its version is known, that TCP port 2012 is blocked except from admin jump hosts, and that someone has hunted back to August. vCenter 7.0 has no public fix, so it needs isolation and an upgrade plan now. If a compromise is found, CERT-In must be told within 6 hours under Section 70B.

For security analysts

CVE-2026-123890, CVSS 9.8 Critical (VMware score; NVD analysis pending), CWE-288. Unauthenticated authentication bypass in the vmdir DCE/RPC interface on TCP 2012: predictable timestamps in the SRP login let the attacker recover the session key and act as administrator@vsphere.local. Exploitation: yes, zero-day used by ARMORY CASTLE from early September 2026 (Mandiant, GTIG). Public proof of concept: not stated. Tooling: BONESAW copies the vmdir database, hijacks the SAML token service and creates SSO admin accounts. Overlaps CVE-2026-59309 (29 July 2026), which also leaked the SRP session key. Fixed: vCenter 9.1.1.0200, 9.0.2.0200, 8.0 U3m; VCF 5.2.5 (KB88287). vCenter 7.0: no public fix. Steps: 1) block TCP 2012 except from admin jump hosts and vCenter/PSC nodes; 2) patch vCenter, then the SDDC Manager and VMware Tools flaws in VMSA-2026-0009; 3) isolate 7.0 and plan upgrade. Hunt back to August: unexpected SSO admins, administrator@vsphere.local logins from unusual hosts, STS or SAML certificate changes, large vmdir reads, TCP 2012 from non-vCenter hosts, unknown Go binaries such as /tmp/123. Logs: /var/log/vmware/vmdird/, /var/log/vmware/sso/. If compromised: isolate, preserve logs, remove rogue accounts, replace STS signing certificate, reset administrator and service passwords, check ESXi and VMs for persistence, engage DFIR. CISA KEV: not stated.

Key points

CVE ids covered: CVE-2026-123890, CVE-2026-123892, CVE-2026-123893, CVE-2026-59309

The full report is a PDF that opens with a work email.