Google: ARMORY CASTLE Exploited VMware vCenter Zero-Day CVE-2026-123890, Affecting vCenter 7.x and 8.x; Broadcom Has Released a Patch

Google Threat Intelligence Group and Mandiant say ARMORY CASTLE, a suspected China-nexus actor, exploited the vCenter authentication bypass CVE-2026-123890. VMware disclosed it on November 19, and Google urges affected organizations to apply Broadcom's patch immediately.

News date: About 6 min read

Share on LINE
Contents
  1. 1. What is CVE-2026-123890, and which versions are affected?
  2. 2. How did ARMORY CASTLE operate in this incident?
  3. 3. How does it differ from the earlier CVE-2026-59309, and why does the timing matter?
  4. 4. How can enterprise administrators reduce risk?

Google Threat Intelligence Group (GTIG) and Mandiant have published an analysis describing how ARMORY CASTLE, a suspected China-nexus threat actor, exploited the VMware vCenter vulnerability CVE-2026-123890 in an intrusion. It is a "zero-day," meaning the attacker was already exploiting it before the vendor disclosed and patched it. According to Google, VMware disclosed the flaw on November 19, 2026, and Broadcom has released a security patch. For organizations running virtualized environments, vCenter is the control hub that centrally manages ESXi hosts (the servers that run virtual machines); once an attacker gains administrative control, the impact can extend across the entire virtualized environment. All attack details and assessments below come from Google's analysis.

What is CVE-2026-123890, and which versions are affected?

Google explains that vSphere consists of ESXi and vCenter Server, and that vCenter is a centralized management platform deployed as a Photon Linux virtual appliance. CVE-2026-123890 is described as an unauthenticated SRP-6a session key leak over DCE/RPC (a communication method that lets programs call remote functions across a network); SRP-6a is a login authentication protocol that does not transmit the password directly. Successful exploitation bypasses remote authentication and creates an authenticated session as administrator@vsphere.local, in other words logging in as the highest-privileged administrator without a password.

Google states that once an attacker holds an administrator session, they can run arbitrary commands and retrieve files, including the data.mdb database. Google also says the BONESAW tool achieves full system compromise of vCenter Server 7.x and 8.x appliances. Google's article does not list specific patched version numbers, so readers should consult Broadcom's advisory.

How did ARMORY CASTLE operate in this incident?

According to Google, ARMORY CASTLE previously exploited the BeyondTrust Remote Support zero-day CVE-2026-102764 (patched in BT26-05), and this article describes its follow-on activity. The attacker moved laterally (hopping from one compromised machine to others on the internal network) from the Remote Support appliance to internal Linux appliances lacking EDR (endpoint detection and response, security software that monitors computers for abnormal behavior), deployed several pieces of malware, and then used BONESAW against the internal vCenter server, ultimately reaching ESXi hosts and guest virtual machine data.

Google says this campaign deployed five newly identified malware families and tools (SLIMSAVAGE, CAGEMATCH, BEARBONES, BONESAW and SAWSNAKE), along with the previously seen LAZYBONES backdoor. Google notes that SAWSNAKE can support Golden SAML attacks against vCenter, that is, stealing the key used to sign login credentials and then forging credentials oneself, which allows forged authentication tokens, bypassing multi-factor authentication and impersonating any user.

Google also says the attacker temporarily enabled SSH on vCenter through the VAMI API (the programmatic interface of the vCenter appliance management interface), stole the internal master key file and the PostgreSQL password file, then turned SSH off again, and afterward accessed ESXi and enumerated the file system and virtual machine data. Google attributes the activity to ARMORY CASTLE, a suspected China-nexus espionage actor.

How does it differ from the earlier CVE-2026-59309, and why does the timing matter?

Google's comparison of the two vCenter vulnerabilities (compiled from the Google Cloud blog)
ComparisonCVE-2026-123890CVE-2026-59309
Vulnerable componentDCE/RPC interface of vmdirvCenter vmdir daemon
Mechanism described by GoogleLeaks the SRP session key by exploiting predictable UUIDv1 timestamps in the SRP authentication interfaceBypasses authentication by building LDAP packets with a malformed authorization token
Related portport 2012 (rpc_srp_verifier)TCP 389 or 636
Disclosure dateNovember 19, 2026 (VMware)July 29, 2026

Google believes ARMORY CASTLE may have known about CVE-2026-123890 before CVE-2026-59309 was disclosed: in early September, BONESAW was run against a vCenter that had already been patched for CVE-2026-59309, and the Go program's build timestamp is 2026-07-13T09:21:24Z, 16 days before the July 29 disclosure. This means a vCenter that was only patched for the older flaw could still be compromised. Google also cautions, however, that Go build metadata can be modified before compilation.

How can enterprise administrators reduce risk?

Google says reactive patching alone is not enough to protect vCenter, and recommends zero-trust-style infrastructure hardening (trust no connection by default and open only necessary access), along with Mandiant's "vSphere and BRICKSTORM Malware: A Defender's Guide." Google also explains that the VCSA's native VAMI firewall lacks port-level granularity, that the management interface itself sits on port 5480 and so can be shut off by an attacker, that it does not generate remote deny logs, and that it does not manage outbound traffic.

Google says Mandiant has published IOCs (indicators of compromise, such as suspicious IPs and file names) in a GTI Collection (registered users only) and provides YARA rules (detection rules that match characteristics of malicious files). Google SecOps customers can use the related rule packs, for example detection of "VMware vCenter VAMI API SSH Enablement." Google also mentions that detection of this activity covers behaviors such as suspicious curl downloads to /tmp.

Frequently asked questions

Has this vulnerability been patched?

According to Google, Broadcom has released a security patch, and Google strongly recommends affected organizations apply it immediately. The article does not list specific version numbers, so rely on Broadcom's official advisory.

Which vCenter versions are affected?

Google says BONESAW achieves full compromise of vCenter Server 7.x and 8.x appliances; the article also says CVE-2026-123890 affects VMware vCenter Server deployments.

Is this a confirmed nation-state attack?

Google attributes the activity to ARMORY CASTLE, a "suspected" China-nexus espionage actor. This is Google's assessment, not a confirmed conclusion.

Do ordinary users need to worry?

The article focuses on enterprise vCenter and virtualized environments; Google does not discuss any impact on ordinary consumers. Organizations that manage vSphere should prioritize reviewing the patching and hardening recommendations.

Browse the latest news in this topic

Found this guide helpful? Share it with someone who needs it

Share on LINE

Sources

Compiled from the references and verification dates listed above; fares, schedules, product features, and terms can change, so please confirm the latest details on the relevant official website before travelling, booking, or purchasing.

Lifestyle