How to tell if your VMware vCenter was hit (CVE-2026-123890)
Quick answer: CVE-2026-123890 (CVSS 9.8) is an authentication bypass in vCenter’s Directory Service. An attacker who can reach the right network port can get an administrator session without a password. Google and Mandiant say Armory Castle used it as a zero-day after first breaking into a BeyondTrust Remote Support appliance. Broadcom shipped fixes Nov 19. If you run vCenter, patch it, limit who can reach it, and review it for new admin accounts. (The Hacker News)

Affected: VMware vCenter Server 7.0, 8.0 and 9.x, and the VMware Cloud Foundation / vSphere Foundation bundles that include it, until patched. Fix: Broadcom’s Nov 19, 2026 patches: 9.1.1.0200, 9.0.2.0200, 8.0 U3m, and Cloud Foundation 5.2.5. vCenter 7.0 needs Broadcom Support on an extended contract. Telco Cloud products: Broadcom KB463116. Exploited yet? Yes. Google Threat Intelligence Group and Mandiant attribute zero-day exploitation since early September 2026 to a suspected China-nexus group, Armory Castle.
Am I affected?
You are in scope if you run vCenter Server, or a VMware Cloud Foundation, vSphere Foundation or Telco Cloud product that includes it, on a build older than the fixed versions above. Home labs and small shops count too. If you only use ESXi with no vCenter, this specific bug is not your entry point, although the attackers went on to ESXi hosts after taking vCenter. (The Hacker News)
What the attackers did
Google and Mandiant describe one campaign with two zero-days:
- Front door: a BeyondTrust Remote Support flaw (CVE-2026-102764, CVSS 9.3), used for recon, admin control and persistence.
- Pivot: from there to an internal Linux appliance, then root, then scans for VMware-specific ports (9080, 5480 and 2012; 2012 is the vCenter Single Sign-On control port).
- vCenter: a Go tool called BONESAW used CVE-2026-123890 to get an administrator session as
[email protected], copy the directory database, and create a new SSO administrator. A second tool, SAWSNAKE, forged login tokens, which lets an attacker bypass multi-factor authentication and impersonate any user. - Hosts: they turned on SSH on the vCenter appliance, created a local admin account, then went into ESXi hosts, mounted VM storage and added their own SSH key to root.
Google says it suspects the group knew of the flaw before a related bug (CVE-2026-59309) was disclosed July 29, because the BONESAW binary carries a July 13 build timestamp, but notes build metadata can be altered. (The Hacker News, quoting Google/Mandiant)
How to check
- Version: in the vSphere Client or the appliance management page (port 5480), compare your build to the fixed list above.
- Exposure: confirm vCenter, its management interface and the SSO ports are not reachable from the internet or from untrusted network segments. Broadcom’s advisory VMSA-2026-0009 lists no workaround, so network limits only reduce exposure.
- Signs of compromise (from the Google report, not a complete list): unexpected administrator or SSO accounts, such as a local admin named
sps-at@vsphere.local; SSH switched on for the vCenter appliance when you did not do it; unfamiliar keys in ESXi rootauthorized_keys. Also review any BeyondTrust Remote Support appliance, since that was the way in.
What to do
- Patch vCenter to a fixed build, then check the other VMware products in your Broadcom advisory.
- Patch or review BeyondTrust Remote Support if you run it (CVE-2026-102764).
- Hunt for the signs above. If you find any, treat the environment as compromised: rotate credentials and SSO and SAML signing material, and bring in incident response.
- Keep management networks private. vCenter should sit on an admin network behind a VPN or jump host.
What is still unknown
Who else was hit. Google has not published a victim count. The reports we read do not list indicators of compromise beyond the tool names and behaviors above.
FAQ
Is this ransomware? The reports describe espionage and data theft, not ransomware. Is it in CISA’s KEV list? We did not confirm it in the sources we read. Check CISA’s catalog. Why does vCenter matter so much? It controls every virtual machine and host under it, so an admin session there is a master key.
Sources
- Broadcom, VMSA-2026-0009 / VMSA-2026-0009.1, “VMware vCenter, Tools, and SDDC Manager updates address multiple vulnerabilities” (issued Nov 19, 2026; updated Nov 20, 2026). Workarounds: None. https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
- Broadcom supplemental FAQ for VMSA-2026-0009: https://brcm.tech/vmsa-2026-0009-qna
- The Hacker News, “China-Linked Hackers Exploit Critical VMware vCenter Zero-Day to Gain Admin Access and Steal Data” (Nov 20, 2026): https://thehackernews.com/2026/11/china-linked-hackers-exploit-critical.html
- Defend Network briefing, Nov 20, 2026 (summary of Broadcom VMSA-2026-0009 and reports): https://defend.network/briefings/vmware-venter-php-rce-asus-critical-exploits-2026-11-20.html
AltTab Dad
