Suspected China-Nexus Group Exploits VMware vCenter Zero-Day; CISA Sets Nov. 23 Deadline
Google Threat Intelligence Group describes CVE-2026-123890, a vCenter flaw exploited in early September. CISA added it to its catalog on Nov. 20.
VMware disclosed CVE-2026-123890 on Nov. 19, 2026, an authentication bypass in the VMware Directory Service that affects vCenter Server. Google Threat Intelligence Group says a suspected China-nexus group it calls Armory Castle exploited the flaw as a zero-day in early September 2026, before public disclosure.
The U.S. Cybersecurity and Infrastructure Security Agency added the flaw to its Known Exploited Vulnerabilities catalog on Nov. 20, with a due date of Nov. 23. Google says the activity reached vCenter and then ESXi hosts, and that a BeyondTrust Remote Support zero-day, CVE-2026-102764, was exploited in the same campaign.
Which vCenter Versions Are Affected and What Is Fixed
Google describes it as an unauthenticated Secure Remote Password (SRP-6a) session key disclosure flaw in the vmdir DCE/RPC interface, which is reached over port 2012. Google says BONESAW achieves full system compromise against vCenter Server 7.x and 8.x appliances through this flaw.
Google says the flaw relies on predictable UUIDv1 timestamp generation in the authentication interface. Exploitation can produce an authenticated session as [email protected], from which an attacker can run commands and retrieve files.
Google recommends that affected organizations immediately apply the security patches provided by Broadcom.
CISA’s catalog links to Broadcom security advisory 39495 for this flaw.
CISA Catalog Entry
CISA’s Known Exploited Vulnerabilities catalog lists CVE-2026-123890 with a date added of Nov. 20, 2026, and a due date of Nov. 23, 2026.
How the Intrusion Spread From vCenter to ESXi Hosts
Google says ARMORY CASTLE exploited a BeyondTrust Remote Support zero-day, CVE-2026-102764, in the same campaign, and that the flaw was patched in BT26-05.
Google says the group used a Go utility it calls BONESAW to exploit the vCenter flaw. Google says BONESAW exfiltrates the LMDB database, hijacks the SAML Security Token Service and creates an SSO Administrator account. Google adds that BONESAW extracted the token service’s SAML signing key and forged SAML assertions.
The attackers also created a local administrator account on vCenter and enabled SSH through the VAMI API. Google says the group then executed BEARBONES, a backdoor, to open listeners on TCP port 53 and later on TCP port 33992.
Google says the activity reached the ESXi hosts that vCenter manages. The attackers mounted VMFS volumes and added an SSH key to the root account’s authorized keys. Google says the group used a tool to pull NTDS.dit and registry hives from guest virtual machines, and staged the data in a hidden directory before exfiltration.
The group also deployed web shells and LAZYBONES, a backdoor that uses Slack for command and control.
Timeline and Attribution Behind the Campaign
Google attributes the activity to a suspected China-nexus espionage group it calls ARMORY CASTLE, formerly tracked as UNC5221. It notes an overlap with UNC6201 (BRICKSTORM) in one SSH-enablement technique but does not attribute the activity to that group.
Google gives the BONESAW build timestamp as July 13, 2026, and says build metadata can be modified. CVE-2026-59309, an LDAP authorization-token bypass, was disclosed on July 29, 2026. Google says BONESAW ran in early September 2026 against a vCenter already patched for that earlier flaw, and that Mandiant has evidence ARMORY CASTLE knew of CVE-2026-123890 before that disclosure.
Google’s earlier report on the BeyondTrust activity was published Oct. 15, 2026. VMware disclosed CVE-2026-123890 on Nov. 19, 2026, the same day as Google’s post.
Google recommends firewall rules that stay independent of VAMI, so an attacker cannot disable them through the web application.
CISA’s Nov. 23 Deadline and Google’s Hardening Advice
CISA’s catalog lists CVE-2026-123890 with a date added of Nov. 20, a due date of Nov. 23, and a requirement for forensic triage. The required action is to apply mitigations in line with vendor instructions.
The entry also refers to BOD 26-04, a directive on prioritizing security updates by risk. The catalog says to follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable, and to assess each asset’s internet exposure.
CISA added three other flaws the same day, each due Nov. 23. Cisco Expressway CVE-2026-76466 involves hard-coded credentials that let an unauthenticated remote attacker run commands as root on a clustered device. Apache Roller CVE-2026-129448 is an unsafe deserialization flaw in the XML-RPC endpoint. SAP NetWeaver CVE-2025-42884 is a JNDI lookup injection flaw in the Enterprise Portal. Cisco Expressway and Apache Roller carry forensic triage requirements; the SAP entry does not.
Google recommends applying Broadcom’s patches immediately and hunting with its indicators of compromise, which are available to registered users, and its YARA rules. It advises testing any iptables changes and running them under formal change control.
Google recommends firewall rules that stay independent of VAMI, so an attacker cannot disable them through the web application. Its hardening guidance also describes default-deny inbound and egress rules and limits on access to ports 443, 2012, 22 and 5480.




