VMware vCenter CVE-2026-123890 Was a Zero-Day for Two Months: China-Linked ARMORY CASTLE Forged Golden SAML, Took Over ESXi and Pulled AD Secrets From VM Disks

Critical · 2026-11-20 · By H.A

VMware vCenter CVE-2026-123890 Was a Zero-Day for Two Months: China-Linked ARMORY CASTLE Forged Golden SAML, Took Over ESXi and Pulled AD Secrets From VM Disks

Google and Mandiant say suspected China-nexus group ARMORY CASTLE exploited the vCenter vmdird authentication bypass CVE-2026-123890 since early September, chaining a BeyondTrust zero-day, six custom tools and Golden SAML to steal domain secrets straight from virtual machine disks.

Overview

Google Threat Intelligence Group (GTIG) and Mandiant say the critical VMware vCenter authentication bypass that Broadcom patched on 19 November, CVE-2026-123890 (CVSS 9.8), was used as a zero-day for at least two months. They attribute the attacks to ARMORY CASTLE, a suspected China-nexus espionage group formerly tracked as UNC5221. The report, published on 20 November 2026, is the first public evidence that the bug was exploited before the fix. Our earlier coverage of VMSA-2026-0009 dealt only with the patch. What's new is the full intrusion chain, six malware families and utilities, network indicators and detection rules.

The investigators say a "small number" of organisations are confirmed compromised and more are probably affected. The group did not attack vCenter from the internet. It got in through an earlier BeyondTrust Remote Support zero-day (CVE-2026-102764), moved to an internal Linux appliance with no endpoint monitoring, and attacked vCenter from inside. From there it forged administrator sessions, took over ESXi hosts and pulled domain-controller secrets straight out of virtual machine disks.

The Vulnerability

CVE-2026-123890 is in the VMware Directory Service (vmdird) on the vCenter Server appliance. GTIG describes it as an unauthenticated SRP-6a session key disclosure over DCE/RPC on TCP port 2012, caused by predictable UUIDv1 timestamp generation in the SRP interface. Anyone who can reach that port can get an authenticated session as administrator@vsphere.local without a password.

Broadcom's VMSA-2026-0009 (19 November) bundles the fix with four other issues, in SDDC Manager and in VMware Tools for Windows, and lists no workaround. Fixed builds reported for the vCenter bug include vCenter 8.0 U3m, VCF/vSphere Foundation 9.0.2.0200 and 9.1.1.0200, and VCF 5.2.5. Check the advisory for your exact build. Organisations still on vCenter 7.0 should contact Broadcom about extended support.

When this was written, CVE-2026-123890 was not yet in CISA's Known Exploited Vulnerabilities catalog. Given GTIG's findings, we expect it to be added.

Timeline

Tradecraft

Indicators of Compromise

GTIG describes the IPs below as suspected obfuscation-network addresses. They are likely compromised or rented relays, so match on them for hunting and don't treat them as proof of attribution.

Detection

# On the vCenter appliance (VCSA shell): defensive checks
find / -xdev -perm -4000 -name env 2>/dev/null
ss -tlnp | grep -E ':(53|33992)\b'
grep -rl 'vmtoolscs' /etc/systemd /usr/lib/systemd 2>/dev/null
# On each ESXi host
cat /etc/ssh/keys-root/authorized_keys

Recommended Actions

Analyst Assessment

This campaign repeats a pattern ARMORY CASTLE has used since 2023: break into an edge or security appliance, then move to infrastructure that EDR cannot see. Owning vCenter gives access to every VM disk, so the group could take domain secrets without running a single command inside a Windows guest. That defeats most endpoint detection. The BONESAW build date and its use against a host patched for the July vmdir bug point to deliberate research into the same component, so follow-on vCenter bugs are likely. Severity is Critical: the bug is unauthenticated, it has been exploited by a capable state-linked actor, and there is no workaround. Patching alone does not remove an attacker who is already inside, so hunting matters as much as the update.

Sources

REEF SENTINEL