Tech • AI • Robotics • Game

ENFR

Full article — scored 10/10

China-linked hackers exploit critical VMware vCenter zero-day

A China-linked espionage actor tracked as ARMORY CASTLE used a critical VMware vCenter Server zero-day, CVE-2026-123890, to obtain administrator-level access, steal directory data and extend control inside virtualized enterprise environments before Broadcom’s November 19, 2026 patches were released.

Sign in to follow
Generated November 20, 2026 at 8:38 AM≈ 7 min read
Original source — The Hacker News RSS
China-linked hackers exploit critical VMware vCenter zero-day

A critical vCenter flaw, already used before disclosure

Broadcom’s November 19, 2026 VMware security release has turned into an emergency response event for enterprise infrastructure teams after Google Threat Intelligence Group and Mandiant detailed exploitation of CVE-2026-123890 by ARMORY CASTLE, a suspected China-linked espionage group formerly tracked as UNC5221 . The vulnerability affects VMware vCenter Server, the management plane used to configure and administer ESX/ESXi hosts and the virtual machines running on them .

The core risk is straightforward: CVE-2026-123890 is an unauthenticated authentication-bypass flaw in the VMware Directory Service component of vCenter, rated critical with a CVSS 3.1 score of 9.8 . Rapid7 described the issue as a VMware Directory Service authentication bypass that can be exploited by an attacker with network access to affected vCenter systems, without credentials, to gain unauthorized access as the Administrator user . For defenders, that means the vulnerable asset is not just another server; it is the administrative control plane for large parts of the data center.

Google and Mandiant said ARMORY CASTLE exploited the flaw in early September 2026 using a custom Golang utility called BONESAW . That timeline matters because Broadcom’s fixes arrived on November 19, 2026, meaning the vulnerability was used as a zero-day for more than two months before public patch availability . SecurityWeek also reported that Mandiant privately reported the bug to Broadcom and linked exploitation to ARMORY CASTLE, while Broadcom’s advisory itself did not state that in-the-wild exploitation had occurred .

How the attackers reached administrator access

According to the Google and Mandiant analysis, CVE-2026-123890 is an unauthenticated Secure Remote Password session-key disclosure vulnerability over DCE/RPC . Successful exploitation creates an authenticated session as administrator@vsphere.local, allowing the attacker to execute commands and acquire files, including the data.mdb directory database through the vCenter Server Directory Service RPC interface . BONESAW was built to automate that path: exfiltrating the LMDB directory database, hijacking the SAML Security Token Service and creating a Single Sign-On administrator account .

Mandiant observed ARMORY CASTLE first move laterally from a compromised BeyondTrust Remote Support appliance into internal Linux appliances, then escalate privileges to root and stage additional tooling for persistence, lateral movement and VMware reconnaissance . The group scanned for VMware-related services and ports, including the vCenter SSO control interface on port 2012, which Google said was integral to exploiting CVE-2026-123890 through BONESAW . Once BONESAW was deployed, the attackers used it against an internal vCenter server, created an SSO administrator account, exfiltrated and parsed the directory database and enabled further movement .

The post-exploitation toolkit was broader than a single exploit binary. Google and Mandiant identified SLIMSAVAGE and CAGEMATCH webshells, the BEARBONES backdoor, the BONESAW exploitation utility and the SAWSNAKE SAML utility, with LAZYBONES also observed in earlier ARMORY CASTLE activity . SecurityWeek reported that the attackers also used tooling to forge SAML tokens, installed backdoors, took vCenter master encryption material and database credentials, and later moved to an ESXi host to collect more information .

Why vCenter compromise is different from ordinary server compromise

A vCenter server concentrates identity, configuration and operational control. A successful administrator session can expose host inventories, VM configuration, directory objects, SSO configuration, service accounts and secrets that support lateral movement. In this case, the reported theft of the LMDB directory database and SAML signing material raises the risk from one-time access to durable control over identity assertions and privileged accounts .

That is why CVE-2026-123890 is more dangerous than a narrow application bug. Google and Mandiant wrote that BONESAW can stream the underlying LMDB file, extract the VMware Security Token Service SAML private RSA signing key, create a backdoor machine account, forge administrative SAML assertions and assign Global Administrator privileges through the vSphere SOAP API . In plain language, the attackers were not simply opening a console; they were trying to seize the trust fabric that vCenter uses to decide who is an administrator.

The issue is also distinct from CVE-2026-59309, another vCenter authentication-bypass vulnerability disclosed earlier in 2026 . Broadcom’s supplemental guidance says CVE-2026-123890 is a new and separate issue and that systems below the fixed versions need the new update even if they were patched for the earlier July vulnerability . Google and Mandiant said BONESAW was executed in early September against a vCenter server already patched for CVE-2026-59309, which underlines why defenders cannot treat the November update as optional follow-up maintenance .

Patch status and affected versions

Broadcom’s supplemental VMSA-2026-0009 guidance says the advisory covers five vulnerabilities across vCenter, SDDC Manager and VMware Tools for Windows, with individual CVSS scores ranging from 6.7 to 9.8 . The vCenter issue is CVE-2026-123890, and Broadcom characterizes the required vCenter update as an emergency change requiring prompt organizational action . NHS England’s National Cyber Security Operations Centre assessed further exploitation as highly likely and instructed affected organizations to apply Broadcom’s fixes .

The fixed vCenter and platform versions identified in current remediation guidance are vCenter 9.1.1.0200 for 9.1.x, vCenter 9.0.2.0200 for 9.0.x, vCenter 8.0 U3m for 8.0, and VMware Cloud Foundation 5.2.5 for 5.x deployments . vCenter 7.0 is end of support and has no public patch path in the same way; Rapid7 and NHS England both point extended-support customers to Broadcom support for guidance . Telco Cloud Platform and Telco Cloud Infrastructure customers are directed to Broadcom’s product-specific remediation guidance, with vCenter 8.0 U3m listed as the fixed version for the affected Telco Cloud combinations .

There is no official workaround for CVE-2026-123890 in the guidance reviewed by Rapid7, and the vendor FAQ emphasizes installing the fixed versions rather than relying on configuration changes . Rapid7 also noted that the update is not eligible for vCenter Quick Patch and should be prioritized outside normal patch cycles where necessary . Broadcom’s FAQ says running workloads are not the issue: updating vCenter temporarily affects management interfaces, but virtual machines and container workloads continue running .

What defenders should do now

The first priority is inventory. Security teams should identify every vCenter instance, including standalone deployments and vCenter components embedded in VMware Cloud Foundation, vSphere Foundation and Telco Cloud environments . The affected list includes vCenter and related product stacks prior to the fixed versions, and Broadcom’s FAQ warns that organizations are likely affected if they run relevant products below those versions .

The second priority is patching with urgency. Because ARMORY CASTLE exploitation began in early September 2026, patching on November 19 or later closes one door but does not prove the environment was never entered . Administrators should preserve logs where possible before maintenance, then update vCenter to the fixed release line and verify the build afterward. Environments running vCenter 7.0 require special attention because the normal public fixed-version path does not apply .

The third priority is compromise assessment. Defenders should review vCenter SSO administrator accounts, machine accounts, SAML trust material, unexpected changes to vSphere permissions, SSH access, VAMI API activity and access to sensitive files such as directory databases and encryption or database credential files. Google and Mandiant’s case showed attackers creating SSO administrator access, exfiltrating the LMDB database, targeting SAML signing material and collecting vCenter master encryption and PostgreSQL credentials .

The fourth priority is containment architecture. Google and Mandiant warned that default vCenter appliance firewall approaches can be too coarse for a Zero Trust model because broad IP trust can expose sensitive management interfaces if an internal server is compromised . Organizations should restrict management-plane access to tightly controlled administrative workstations, segment backup servers and appliances, monitor traffic to vCenter-specific ports and treat internal Linux appliances without EDR as potential staging points .

The larger signal

ARMORY CASTLE’s vCenter exploitation shows a shift from edge-appliance intrusion toward deeper control-plane compromise. In the same campaign, Google and Mandiant said the group used two zero-days and multiple malware families tailored to different systems, indicating significant resources and platform-specific expertise . For enterprise defenders, the lesson is not only to patch vCenter quickly. It is to treat virtualization identity, SSO keys, management APIs and appliance-to-appliance paths as crown-jewel assets that require the same level of monitoring and isolation as domain controllers.

The current state is therefore clear: CVE-2026-123890 is patched, but it was already exploited before disclosure; the documented actor is ARMORY CASTLE; the observed objective included administrator access and data theft; and organizations running affected VMware infrastructure should both update and hunt for evidence dating back to at least early September 2026 .

Sources from the last 72 hours

  1. [1]ARMORY CASTLE Exploits vSphereNov 19, 2026, 1:00 AM
  2. [2]VMSA-2026-0009: Questions & AnswersNov 19, 2026, 1:00 AM
  3. [3]Critical Zero-Day Vulnerability in VMware vCenterNov 19, 2026, 5:29 PM
  4. [4]CVE-2026-123890: Critical Authentication Bypass in VMware vCenterNov 19, 2026, 1:00 AM
  5. [5]VMware patches vCenter zero-day exploited in attacks since SeptemberNov 20, 2026, 1:26 AM
  6. [6]Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APTNov 19, 2026, 8:21 PM

AI-generated article based on recent web research, then preserved as a dated editorial snapshot.