Back Cyberkendra Chinese Hackers Exploited vCenter Zero-Day CVE-2026
Broadcom has patched a critical VMware vCenter authentication bypass, CVE-2026-123890, that Google’s Mandiant says a China-nexus espionage group exploited as a zero-day from early September 2026, more than two months before a fix existed.
CVE-2026-123890 sits in the VMware Directory Service (vmdir), the identity store behind vCenter single sign-on, and carries a CVSS v3 score of 9.8. Broadcom’s VMSA-2026-0009 , published on Thursday, November 19, says an attacker with network access to vCenter can bypass authentication and gain unauthorized access.
The flaw affects vCenter 8.0, 9.0 and 9.1, along with VMware Cloud Foundation (VCF), vSphere Foundation and the Telco Cloud platforms built on them.
On the same day, Mandiant and Google Threat Intelligence Group (GTIG) attributed the attacks to ARMORY CASTLE, the group previously tracked as UNC5221. Broadcom credits Mandiant with reporting CVE-2026-123890, but its advisory does not mention in-the-wild exploitation.
Broadcom also published a second critical advisory, VMSA-2026-0010 , for an Apache HTTP Server flaw bundled in Aria Operations, VCF Operations and VCF Operations HCX. As of November 20, those products have no patch, only a workaround that turns off HTTP/2.
How ARMORY CASTLE Exploited the vCenter Zero-Day
Mandiant’s investigation describes an intrusion that began at a BeyondTrust Remote Support appliance, compromised through CVE-2026-102764, a separate zero-day that CISA added to its Known Exploited Vulnerabilities (KEV) catalog on October 16. From there, ARMORY CASTLE moved to an internal Linux appliance that had no endpoint detection and response (EDR) agent and scanned the network for VMware services, including TCP port 2012.
CVE-2026-123890 leaks a Secure Remote Password (SRP) session key, the secret produced during vmdir’s password-based login handshake, over the directory service’s RPC interface on port 2012. An attacker holding that key gets a session as [email protected] , the built-in vCenter super-admin, without knowing the password.
The group exploited CVE-2026-123890 with a Go-based tool Mandiant calls BONESAW, which ARMORY CASTLE had named vcenter-db-teamcheck-go. BONESAW copied and parsed vCenter’s directory database, stole the SAML signing key vCenter uses to vouch for logins, and created a new SSO administrator account. Mandiant describes the tool as a significant expansion of the group’s use of zero-days after initial compromise.
With the signing key in hand, a second tool, SAWSNAKE, forged SAML tokens, so the attackers could sign in as any vCenter user. ARMORY CASTLE then enabled SSH on the vCenter appliance, took its master key and PostgreSQL database credentials, and disabled SSH again. Mandiant also reports the group pulled Active Directory database files straight from the virtual disks of guest VMs.
For persistence, ARMORY CASTLE deployed BEARBONES, a backdoored Dropbear SSH server that logs passwords; LAZYBONES, a Slack-controlled backdoor Mandiant saw in an earlier ARMORY CASTLE intrusion; and two JSP web shells, SLIMSAVAGE and CAGEMATCH. Mandiant has not named the victim and says BONESAW was likely built for broader operations, so other organizations may have been hit.
CVE-2026-123890 is not a repeat of CVE-2026-59309, the vmdir authentication bypass Broadcom fixed in VMSA-2026-0006 in July. Broadcom’s VMSA-2026-0009 FAQ calls the new bug a separate issue, and Mandiant reports that BONESAW targeted a vCenter server already patched for the July flaw. A second bug from that July advisory, CVE-2026-59310, was added to KEV on August 18 and has since been used in ransomware attacks.
Which vCenter, SDDC Manager, and VMware Tools Versions Have a Fix
For CVE-2026-123890, Broadcom fixed vCenter in 9.1.1.0200 for the VCF and vSphere Foundation 9.1 line, 9.0.2.0200 for the 9.0 line, and 8.0 U3m for vCenter 8.0. VCF 5.x customers get the fix in VCF 5.2.5, which applies vCenter 8.0 U3m, and Telco Cloud Platform and Telco Cloud Infrastructure customers are directed to KB463116. Broadcom lists no workaround.
vCenter 7.0 is not in the VMSA-2026-0009 response matrix. Broadcom’s FAQ tells customers to presume it is affected, since it reached End of General Support on October 2, 2025, and to request a patch through an active extended support contract. Older releases, including vSphere 6.5 and 6.7, should also be treated as vulnerable. ESX hosts are not affected by this advisory.
VMSA-2026-0009 also fixes three SDDC Manager flaws reported by Arnoldas Radisauskas of NATO’s NCSC: an SQL injection that lets an authenticated attacker read and write the database (CVE-2026-123891, CVSS 8.1), an authenticated command injection (CVE-2026-123892, CVSS 7.2) and a local privilege escalation from administrator to root (CVE-2026-123893, CVSS 6.7). SDDC Manager 9.1.1.0200 fixes all three, as do 9.0.2.0100 for the 9.0 line and VCF 5.2.5.
The fifth bug, CVE-2026-123894 (CVSS 6.7), is a SAML token signature bypass in VMware Tools for Windows, reported by Noam Pomerantz. A local privileged process inside a Windows guest configured with guest alias mapping can use it to raise its privileges within that VM. VMware Tools 13.1.5.0 fixes the 13.x branch and 12.5.5 fixes 12.x and 11.x, with 12.4.10 covering 32-bit Windows. Broadcom’s FAQ says stopping or uninstalling Tools is not a workaround.
Organizations in the middle of upgrades face a catch. Broadcom’s FAQ says vCenter 8.0 U3m and the new SDDC Manager 9.0.2 build block upgrades to VCF 9.1.1, and suggests waiting briefly for VCF 9.1.2 or moving vCenter to 9.1.1 first and applying the fix there. KB 67077 has the compatibility matrix.
Aria Operations and HCX Still Wait for an Apache Patch
VMSA-2026-0010 covers CVE-2026-119618 (CVSS 9.8), a race condition in the mod_http2 module of Apache HTTP Server that corrupts heap memory while the server assigns response headers, potentially leading to remote code execution. The Apache project fixed it in httpd 2.4.71 on November 11; versions 2.4.55 through 2.4.70 are affected when HTTP/2 is enabled. Anthropic’s OSS Scanner reported the bug on October 26, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research also reported it.
Broadcom says an attacker with network access to VMware Aria Operations or VCF Operations HCX could exploit CVE-2026-119618 to run arbitrary code. Affected releases are VCF Operations 9.x, Aria Operations 8.18.x, Aria Operations 5.x shipped with VCF, and VCF Operations HCX 9.1.x. Every entry in the advisory reads “Patch pending.”
Until patches ship, Broadcom’s KB463005 walks Aria Operations and VCF Operations admins through disabling HTTP/2 in vcops-photon-apache.conf on each node, by hand or with a supplied script, cve-2026-119618.sh. Broadcom says collectors, agents, and the API continue to work, though the UI may feel slower and each Apache restart briefly interrupts access. Every product upgrade overwrites the file and turns HTTP/2 back on, so the check has to be repeated after each upgrade.
For HCX Manager 9.1.x, KB463022 provides a block-http2.sh script that removes the h2 protocol on ports 443 and 9443. Broadcom says the change has no functional impact on running migrations or network extensions.
Is CVE-2026-123890 Being Exploited?
Mandiant says CVE-2026-123890 was exploited in the wild as a zero-day, starting in early September 2026. Broadcom’s advisory and FAQ do not address exploitation, and Cyber Kendra found no KEV entry for CVE-2026-123890 at the time of writing.
Broadcom reports no exploitation of the SDDC Manager and VMware Tools flaws. For the Apache bug, VMSA-2026-0010 does not state an exploitation status, and CVE-2026-119618 was not in the KEV catalog as of November 12. Red Hat says public research has demonstrated a reliable exploit against the default configuration, without naming the research.
What vSphere and Aria Admins Should Do Now?
Broadcom’s FAQ states that “the vCenter issue qualifies under ITIL methodologies as an emergency change.” Patch vCenter to 9.1.1.0200, 9.0.2.0200 or 8.0 U3m, or VCF 5.2.5, and do not assume a July patch for CVE-2026-59309 offers any protection. Keep vCenter off the internet and limit port 2012 to trusted management hosts.
Patching does not evict an attacker who already has the SAML signing key because forged tokens continue to work. Mandiant advises reviewing vCenter SSO for administrator accounts nobody created, checking VAMI logs for SSH being enabled and then disabled, looking for SSH servers on high ports that announce “SSH-2.0-pulsesecure_23345”, and putting EDR on internal Linux appliances.
If compromise is suspected, rotate the vCenter STS signing certificate and all SSO credentials. BeyondTrust Remote Support customers should also confirm that CVE-2026-102764 has been patched.
Aria Operations and VCF Operations admins can check each node with httpd -v and rpm -q --changelog httpd | grep -i CVE-2026-119618 . Broadcom’s KB463005 says Apache 2.4.71 or later, or an older build whose changelog names the CVE, is already fixed; anything else needs HTTP/2 disabled until the patch arrives.
Join the conversation. Ask questions, solutions, and help others.
Be the first to start the discussion!
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
