HomeTech NewsCybersecurityGTIG Says ARMORY CASTLE Exploited vCenter CVE-2026-123890

GTIG Says ARMORY CASTLE Exploited vCenter CVE-2026-123890

Google’s Threat Intelligence Group says a suspected PRC-nexus actor it tracks as ARMORY CASTLE, formerly UNC5221, exploited a critical VMware vCenter authentication bypass, CVE-2026-123890, in early September 2026. The GTIG and Mandiant blog, published on 19 November 2026, ties that use to a wider campaign in which the group “exploited two zero-days, and deployed three sets of malware.” Broadcom’s advisory VMSA-2026-0009, issued the same day, rates the vCenter flaw at CVSSv3 9.8, lists no workarounds, and credits Mandiant for reporting it. The advisory is silent on whether the vulnerability has been exploited.

In brief

  • Broadcom has patched CVE-2026-123890, an authentication bypass in the VMware Directory Service on vCenter, as the lead issue in VMSA-2026-0009. There are no workarounds.
  • Google GTIG says ARMORY CASTLE exploited the flaw in early September 2026, after moving from a BeyondTrust Remote Support device, and used a tool it calls BONESAW.
  • Exploitation is GTIG’s finding, not Broadcom’s. CVE-2026-123890 was not in CISA’s Known Exploited Vulnerabilities catalogue as of the 18 November 2026 release.

Broadcom’s patch for CVE-2026-123890 is a critical authentication bypass

VMSA-2026-0009 is dated 19 November 2026 and is marked critical. Broadcom says VMware vCenter “contains an authentication bypass vulnerability in the VMware Directory Service” and that “a malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system.” That “may exploit” line is the vendor’s generic attack-vector wording. It is not an acknowledgment of in-the-wild use.

Patches are listed as 9.1.1.0200 for the 9.1 line, 9.0.2.0200 for 9.0, 8.0 U3m for vCenter 8.0, and 5.2.5 for VMware Cloud Foundation 5.x. For vCenter 7.0, the matrix says: “Contact Broadcom Support if you have extended support contract.” Telco Cloud products are pointed to a knowledge-base article. The advisory also covers four other flaws, CVE-2026-123891 through CVE-2026-123894, which Broadcom scores between 6.7 and 8.1, including SQL-injection and command-injection issues in SDDC Manager. Those are separate bugs; the exploitation account in the Google blog is about CVE-2026-123890.

GTIG describes vCenter as the central platform for configuring and monitoring ESXi hosts, deployed as a Photon Linux virtual appliance. In its account, a successful attack yields an administrator-level session and, from there, the ability to run commands and take files through the directory service. Administrators should treat that as a reason to install the listed builds, not as a recipe.

The 19 November blog is a follow-up to GTIG’s 15 October write-up of ARMORY CASTLE’s use of a BeyondTrust Remote Support zero-day, CVE-2026-102764. GTIG says the group moved laterally from that appliance, focused reconnaissance on VMware systems, and then exploited CVE-2026-123890 in early September 2026 with BONESAW, a Golang utility “primarily built to facilitate remote exploitation.” The post says the same campaign involved two zero-days and three sets of malware “specifically tailored for operating on targeted devices.”

That is Google’s attribution and Google’s timeline. Broadcom’s advisory thanks Mandiant for the report and otherwise stays silent on who used the bug, when, or whether anyone has. Readers should keep those two documents in separate piles.

The vCenter patch also sits next to other recent hypervisor and China-nexus intrusion stories. CISA has already listed an ESXi logging flaw that it said the China-linked group Warp Panda used as a zero-day, a different VMware product and a different actor. Lumen has described Volt Typhoon exploiting at least four zero-days for access, again a separate campaign. The common thread is that hypervisor and management-plane flaws are being used as a path into virtualised estates, not that those earlier cases involved CVE-2026-123890.

A critical advisory is not the same as a KEV listing

The practical instruction is straightforward: apply the fixed versions in VMSA-2026-0009, and if you are still on vCenter 7.0, ask Broadcom whether an extended-support build is available. There is no workaround to sit behind. GTIG’s account, if accurate, means some environments may already have been reached in September, weeks before the public patch.

What the two official documents leave open is the gap between them. Broadcom has published a critical, remotely reachable authentication bypass with no mitigation other than the patch, and has not said it is being used. GTIG has published a detailed exploitation finding against a named group and has not been echoed, in those terms, by the vendor. Until CISA adds CVE-2026-123890 to the Known Exploited Vulnerabilities list, US federal civilian agencies are not under that particular binding deadline. TSN checked the catalogue on 19 November 2026: version 2026.11.18, released at 19:17:41 GMT on 18 November, still lists 1,786 entries and leaves this CVE out.

That gap will not last if GTIG’s forensic account holds up, but it has not closed yet. The immediate work is to patch vCenter, and to treat Google’s ARMORY CASTLE narrative as a reason to look for prior access, not as a substitute for the vendor’s still-silent advisory.

Related stories

Sources

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

  1. Alberta Tables Bill 42 for 600-Metre Data Centre Setbacks
    Data Centres & Energy

More in this category

Latest stories

  1. Alberta Tables Bill 42 for 600-Metre Data Centre Setbacks
    Data Centres & Energy

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.