Blog / Front Line — part 25 of 25

VMware vCenter zero-day: how Armory Castle took control of virtual estates

· urgentic · 4 min read

Short read

This post covers CVE-2026-123890, a critical VMware vCenter Server flaw that Broadcom patched on 19 November after a suspected Chinese state-backed group, Armory Castle, had been exploiting it since early September. It lets an attacker on the network become vCenter's top administrator without a password, and from there reach every virtual machine it manages.

You'll learn how the attack unfolded, who is exposed, what to patch, and the signs worth hunting for in your own logs.

vCenter is the control panel for a VMware estate. Whoever controls it controls the hosts and the virtual machines on them: domain controllers, file servers, databases, backups. That's why a flaw that hands out vCenter administrator access without a password is about as serious as infrastructure bugs get.

On 19 November, Broadcom released emergency fixes for exactly that. BleepingComputer reports that CVE-2026-123890 lets an unauthenticated attacker with network access to vCenter bypass authentication. SecurityWeek gives it a CVSS score of 9.8 and says it was exploited for more than two months before the patch.

What the flaw is

According to Mandiant and Google Threat Intelligence Group, which reported the bug to Broadcom, the problem is in vCenter's directory service (vmdird). A weakness in how it handles password-based authentication over remote procedure calls on TCP port 2012 leaks the session key, so an attacker never needs to know a password. The result is an authenticated session as administrator@vsphere.local, the built-in top-level account.

Mandiant notes this is a different bug from CVE-2026-59309, a separate vCenter authentication bypass disclosed in July. Armory Castle's exploit was used against a server that had already been patched for that earlier flaw, so being up to date in the summer does not protect you.

How Armory Castle used it

Mandiant tracks the group as Armory Castle (formerly UNC5221), a suspected China-nexus espionage actor known for exploiting zero-days in edge devices such as Ivanti Connect Secure and Citrix NetScaler. In this campaign the chain looked like this:

  1. Way in: exploitation of a BeyondTrust Remote Support zero-day (CVE-2026-102764).
  2. Foothold: a move to an internal Linux appliance, root access, and web shells for persistence.
  3. Reconnaissance: scanning the internal network for VMware-specific ports, including 2012, 5480 and 9080.
  4. vCenter takeover: a custom tool called BONESAW exploited CVE-2026-123890, created a new Single Sign-On administrator account, stole vCenter's directory database and extracted its SAML signing key.
  5. Forged logins: a second tool, SAWSNAKE, used that key to forge authentication tokens, a "Golden SAML" technique that can sidestep multi-factor authentication.
  6. Deeper access: the attackers enabled SSH on vCenter through its management API, took the vCenter master encryption key and database credentials, switched SSH off again, then moved onto ESXi hosts. Mandiant says they extracted data from virtual machines, including Windows Active Directory database files.

Along the way they used several further backdoors, including a modified SSH server and a Go backdoor that takes its commands from a Slack channel. Mandiant says the use of two zero-days and malware built for each platform shows deep expertise and substantial resources.

Who is exposed

Broadcom's advisory, VMSA-2026-0009, says you are affected if you run any version of vCenter, SDDC Manager or VMware Tools for Windows earlier than the fixed versions. That includes vCenter deployed on its own or as part of VMware Cloud Foundation, vSphere Foundation and the Telco Cloud platforms, and it applies whether or not Enhanced Linked Mode is on. Broadcom lists no official workaround.

One awkward detail: Mandiant says BONESAW works against vCenter 7.x and 8.x, but SecurityWeek notes there is no public patch for 7.0, which reached end of general support in October 2025. If you still run 7.0, the upgrade conversation is now urgent rather than routine.

What to do now

  1. Patch vCenter. The fixed versions are 9.1.1.0200, 9.0.2.0200 and 8.0 U3m. Also apply the VMSA-2026-0009 fixes for SDDC Manager and VMware Tools for Windows.
  2. Lock down who can reach vCenter. Management interfaces should only be reachable from a small set of admin hosts, not from the general server network. Mandiant's guidance specifically calls out restricting TCP 2012, 443, 5480 and 22 to allow-listed addresses, and recommends its VCSA Hardening & Logging Tool, which enforces those rules at the operating system level so they can't be switched off through a compromised management interface.
  3. Check your edge devices. This intrusion started on a remote support appliance. Make sure the BeyondTrust fix for CVE-2026-102764 and other edge-device patches are in place.
  4. If you were exposed, assume the worst until you know otherwise. A stolen SAML signing key lets an attacker keep forging logins after you patch. Where compromise is suspected, follow Broadcom's and your incident responders' guidance on rotating vCenter certificates and credentials.

What to look for

Mandiant has published indicators and YARA rules. Even without them, these behaviours are worth hunting for in vCenter, ESXi and network logs from early September onwards:

  • new or unexpected vCenter Single Sign-On administrator accounts
  • SSH being enabled on vCenter through the management API, especially if it is switched off again shortly afterwards
  • sign-ins to the ESXi Host Client or SSH as root that don't match change records
  • new SSH keys added to ESXi root accounts, or hidden directories on datastores
  • internal hosts scanning for ports 2012, 5480 or 9080
  • Linux servers making regular HTTPS connections to Slack or other services they have no business using

Mandiant also recommends forwarding vCenter command and system logs to a central system, because attackers can and do clear local history.

The bottom line

Virtualisation platforms are now a favourite target for well-resourced attackers because one console unlocks everything else. Patch vCenter today, keep its management ports off the wider network, and look back through your logs to September. If something looks wrong, treat it as a full incident, not a missed patch.

  • VMware
  • vCenter
  • CVE-2026-123890
  • Armory Castle
  • zero-day
  • ESXi
  • virtualisation
  • threat intelligence