Armory Castle Exploited VMware vCenter Zero-Day Before November Patch

src-ea89237c

Google Threat Intelligence Group and Mandiant attributed the early September 2026 exploitation of a critical VMware vCenter Server flaw to Armory Castle, a suspected China-nexus espionage group formerly tracked as UNC5221. The vulnerability, CVE-2026-123890, carries a CVSS score of 9.8 and allows authentication bypass in VMware Directory Service. VMware patches addressing the issue were released on November 19.

Successful exploitation can give an unauthenticated remote attacker an administrator session as administrator@vsphere.local. Google and Mandiant described the issue as disclosure of an unauthenticated Secure Remote Password (SRP-6a) session key over Distributed Computing Environment/Remote Procedure Calls (DCE/RPC). The resulting access can enable command execution and acquisition of files from the Directory Service, including its data.mdb database.

Patch coverage spans vCenter and VMware platforms

Administrators should use VMware’s release guidance to identify the applicable fixed version for each deployment. The reported fixes include VMware Cloud Foundation and VMware vSphere Foundation 9.1.x.x in 9.1.1.0200, and their 9.0.x.x branches in 9.0.2.0200. VMware vCenter 8.0 is fixed in 8.0 U3m, while VMware Cloud Foundation 5.2 is fixed in 5.2.5. For VMware vCenter 7.0, customers on extended support contracts are directed to contact Broadcom Support.

The advisory also lists VMware Telco Cloud Platform and VMware Telco Cloud Infrastructure releases using vCenter 8.0 U3m as fixed. The listed TCI and TCP releases include 3.0, 4.x, 5.0.x, 5.1.x and 5.2. Organizations should verify product-specific applicability rather than assume that updating one vCenter instance covers every related platform.

Campaign combined appliance access with specialized tools

Investigators observed Armory Castle using a Go-based utility called BONESAW to exploit the vCenter flaw. According to Google, the tool can remotely extract arbitrary Lightning Memory-Mapped Database (LMDB) data, hijack the SAML Security Token Service, and create a Single Sign-On administrator account. A separate tool, SAWSNAKE, supports vCenter SAML authentication bypass and session-cookie generation, enabling forged authentication tokens and impersonation, including bypass of multifactor authentication.

The vCenter activity formed part of a broader intrusion that also involved a then-zero-day in BeyondTrust Remote Support, CVE-2026-102764, rated CVSS 9.3. The group reportedly used the Remote Support appliance for reconnaissance and administrative control, established persistence, and deployed BARECLAW, a custom proxy tunneler. From there, it moved to an internal Linux appliance, escalated privileges, and expanded access toward the virtualized environment.

Google said the attackers scanned internal systems for VMware-related ports, including 9080, 5480 and 2012. The latter is used for the vCenter SSO control-interface RPC and was relevant to BONESAW’s remote exploitation. Investigators also identified SLIMSAVAGE and CAGEMATCH JSP web shells, used to run commands, stage payloads and maintain a foothold on the Linux appliance.

Follow-on activity reached ESXi files and appliances

Other recovered tools included BEARBONES, a C backdoor based on the open-source Dropbear SSH server, and LAZYBONES, a lightweight Go backdoor that uses Slack for command-and-control. Google reported that BEARBONES can bypass system password authentication and log plaintext credentials. LAZYBONES can support command execution and file transfer, and had previously appeared in a separate intrusion in early 2025 following exploitation of Ivanti Connect Secure flaw CVE-2025-22457.

After gaining access to vCenter, the attackers created a local administrator account, enabled SSH through the vCenter Server Appliance Management Interface, and connected using the new account. They then enumerated the ESXi file system, mounted VMFS volumes, and added an SSH public key to the root account’s authorized keys. Data collected from the ESXi file system was archived and downloaded to the Remote Support appliance for later exfiltration.

For defenders, the immediate priority is applying the relevant November 19 fixes and checking all affected vCenter, Cloud Foundation, vSphere Foundation and Telco Cloud deployments. Given the reported administrator-session creation, SSO manipulation, SSH enablement and ESXi file access, incident review should also consider signs of unauthorized accounts, unexpected appliance access and activity involving vCenter or ESXi filesystems. Google noted that CVE-2026-123890 is the second VMware zero-day Armory Castle exploited in 2026; the group was also reported to have abused CVE-2026-41709, an insufficient-logging flaw in VMware ESX.