Exploited Vulnerabilities

VMware vCenter zero-day CVE-2026-123890: how a China-linked APT went from BeyondTrust to Golden SAML and ESXi

VMware vCenter zero-day CVE-2026-123890 was exploited since September to forge SAML tokens and reach ESXi. The attack chain, IOCs and how to check exposure.

By · · Updated · 6 min read

The VMware vCenter zero-day CVE-2026-123890 is an unauthenticated authentication bypass in the VMware Directory Service, and a suspected China-nexus espionage group exploited it from early September 2026, more than two months before Broadcom shipped a fix. Broadcom published VMSA-2026-0009 on 19 November with a CVSS 9.8 rating and no workaround. The same day, Mandiant and Google Threat Intelligence Group (GTIG) described the intrusion: a BeyondTrust Remote Support hack, a pivot through internal Linux appliances, then vCenter, Golden SAML and ESXi.

What happened

Broadcom says an attacker with network access to vCenter can bypass authentication. Its FAQ calls the vCenter fix an emergency change, says the bug exists whether or not Enhanced Linked Mode is used, and says it is distinct from CVE-2026-59309, the directory service flaw fixed in July. ESX hosts are not affected and need no update. The advisory credits Mandiant and does not mention exploitation.

Mandiant attributes the exploitation to ARMORY CASTLE, formerly tracked as UNC5221. Mandiant CTO Charles Carmakal said the company investigated multiple incidents involving this bug, per SecurityWeek.

Fixed versions from the advisory:

Branch Fixed version
vCenter 9.1.x (VCF / VVF) 9.1.1.0200
vCenter 9.0.x (VCF / VVF) 9.0.2.0200
vCenter 8.0 8.0 U3m
VCF 5.x 5.2.5 (vCenter 8.0 U3m via async patching, KB88287)
vCenter 7.0 Contact Broadcom Support (extended support only)
Telco Cloud Platform / Infrastructure KB463116

The advisory also fixes three SDDC Manager bugs (CVE-2026-123891 to CVE-2026-123893) and CVE-2026-123894 in VMware Tools for Windows. Revision 0009.1 on 20 November clarified the affected Tools versions.

The attack chain, step by step

Based on Mandiant’s report:

  1. Initial access. ARMORY CASTLE exploited CVE-2026-102764, a zero-day in BeyondTrust Remote Support patched in BT26-05, which Mandiant documented in October.
  2. Recon for VMware. From that appliance the group ran nmap against internal subnets for ports 443, 2012, 389, 5480 and 9080,. Port 2012 is the vCenter SSO control RPC interface.
  3. Foothold on Linux appliances without EDR. It dropped the SLIMSAVAGE webshell (ActiveSer.jsp, secret pwd=123) and, about four hours later, the CAGEMATCH staging webshell (u.jsp) that writes uploads to /tmp.
  4. Root. It used gdb to set the SUID bit on /bin/env, the same trick it used on the Remote Support appliance.
  5. The vCenter exploit. BONESAW (/tmp/123, unpacked from 123.rar) is a Go tool that abuses predictable UUIDv1 timestamps in the directory service’s SRP-6a authentication over DCE/RPC on port 2012. That discloses the shared session key and yields a session as administrator@vsphere.local. BONESAW then streams the directory database (data.mdb), extracts the STS SAML signing key, creates an SSO admin account and can grant Global Administrator on the root folder.
  6. Golden SAML. SAWSNAKE (/tmp/sss) forges SAML assertions with the stolen key, which Mandiant says lets the actor bypass MFA and impersonate any user.
  7. Backdoor and vCenter shell. BEARBONES (/tmp/dbr), a backdoored Dropbear SSH server, listened on ports 53 and later 33992. The actor created a local vCenter admin, enabled SSH through a VAMI API PUT to /rest/appliance/access/ssh, took the vCenter master key and the PostgreSQL password file, then turned SSH off again.
  8. ESXi and Active Directory. Using vpxuser and root SSH, it added a key to root’s authorized_keys, staged files in a hidden .a directory on a VMFS volume, and used vmfs_browser.py to pull NTDS, SYSTEM and SECURITY from Windows VM disks. The archive most likely left through the Remote Support appliance. A Slack-based backdoor, LAZYBONES (/usr/bin/vmtoolscs), kept persistence via systemd.

Why it worked

An old patch did not help. BONESAW ran against a vCenter already patched for CVE-2026-59309. Its build timestamp is 13 July 2026, 16 days before that bug was disclosed, though Mandiant notes Go build metadata can be altered.

Blind spots in the middle. The pivot ran through Linux appliances with no EDR, and Mandiant notes the built-in VAMI firewall sends no remote logs for denied connections and leaves egress unmanaged.

vCenter is an identity provider. Once the STS signing key is out, the attacker no longer needs the bug. That is the same lesson as the Check Point zero-day chain: an edge appliance falls first and the real target sits behind it.

What defenders should do

  • Patch vCenter now to the fixed build for your branch. Broadcom says vCenter updates do not stop running workloads. Note the “Back-in-Time” issue: 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1 until 9.1.2.
  • Then hunt. Carmakal’s advice was to apply the patches and examine systems for evidence of compromise.
  • Restrict port 2012, 443, 22 and 5480 on the appliance to allowlisted admin hosts. Mandiant recommends iptables default deny, egress deny and remote syslog, via its VCSA Hardening & Logging Tool, tested under change control.
  • Patch BeyondTrust Remote Support if you have not since October.
  • vSphere 7.0 left general support on 2 October 2025; without extended support there is no public fix.

How to check if you are affected

  1. Version: vSphere Client Summary tab, or in PowerCLI after Connect-VIServer, read $global:DefaultVIServer.Version and $global:DefaultVIServer.Build. Anything below the table above is vulnerable.
  2. Exposure: check which hosts can reach TCP 2012 on vCenter. Mandiant’s attacker reached it from a compromised internal appliance, so “not internet-facing” is not enough.
  3. SSO accounts: look for SSO admin or machine accounts you did not create. Mandiant saw a local admin whose name began with sps- in @vsphere.local.
  4. SSH toggling: look for VAMI calls to /rest/appliance/access/ssh that enable SSH and disable it shortly after.
  5. Files: /tmp/123, /tmp/sss, /tmp/dbr, /tmp/123.key, /tmp/gdb_file, ActiveSer.jsp, u.jsp, /usr/bin/vmtoolscs, and a hidden .a directory on VMFS volumes. Check whether /bin/env has the SUID bit on Linux appliances.
  6. Network: SSH banners SSH-2.0-pulsesecure_23345; outbound HTTPS to the Slack API from appliances. Mandiant’s suspected obfuscation network IPs: 103.147.251[.]5, 103.190.38[.]3, 118.174.128[.]34, 118.174.128[.]36, 118.174.128[.]38, 176.9.89[.]66, 185.71.15[.]109, 220.121.128[.]41, 222.108.77[.]44, 61.216.56[.]127, 81.45.89[.]43.
  7. KEV: update, 21 November: CISA added CVE-2026-123890 to the Known Exploited Vulnerabilities catalog on 20 November 2026, with a due date of 23 November 2026 under BOD 26-04 (the catalog entry is named “VMWare vCenter Authentication Bypass Using an Alternate Path or Channel Vulnerability”, CWE-288, ransomware use “Unknown”). When this article was first published, the catalog (version of 18 November) did not list it. CVE-2026-102764 has been listed since 16 October.

Mandiant’s report also has YARA rules for SLIMSAVAGE, BEARBONES and LAZYBONES.

My take

Patching closes the door, but if you find any of the indicators above, I would treat the vSphere SSO domain as compromised: rotate the STS signing certificate, review every SSO account, and assume the domain controller hashes on your virtual DCs were read. A forged SAML token does not care which build you run.

The bigger point is where this bug was used. It was not the way in. It was a post-compromise zero-day, fired from a box nobody was watching at a port most teams never filter internally. More cases like this are in the exploited vulnerabilities category.

Questions for this week: which hosts can reach port 2012 on your vCenter, do your appliances have EDR or at least remote syslog, and when did you last rotate the vCenter STS certificate?

Sources

  1. VMSA-2026-0009: VMware vCenter, Tools, and SDDC Manager updates address multiple vulnerabilities · Broadcom, 19 November 2026 (updated 20 November)
  2. VMSA-2026-0009: Questions & Answers · Broadcom (VMware on GitHub), 19 November 2026
  3. ARMORY CASTLE Exploits vSphere · Mandiant and Google Threat Intelligence Group, 19 November 2026
  4. Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT · SecurityWeek, 19 November 2026
  5. VMware patches vCenter zero-day exploited in attacks since September · BleepingComputer, 19 November 2026
  6. Known Exploited Vulnerabilities Catalog · CISA
  • vmware
  • vcenter
  • cve-2026-123890
  • vmsa-2026-0009
  • armory-castle
  • unc5221
  • beyondtrust
  • cve-2026-102764
  • bonesaw
  • golden-saml
  • esxi
  • Cloud & Identity