VMware vCenter Zero-Day Exploited for Months Before Emergency Patch

Broadcom rushed out an emergency patch for VMware vCenter on November 19 — and Google’s threat researchers say it came more than two months too late. A suspected China-linked espionage group had already been exploiting the flaw as a zero-day since early September, quietly taking over the management console that controls entire virtualized data centers.

The vulnerability, tracked as CVE-2026-123890, carries a CVSS score of 9.8 out of 10. It is an authentication bypass in the VMware Directory Service, the identity store behind vCenter’s single sign-on system. According to Broadcom’s advisory VMSA-2026-0009, an attacker with network access to vCenter can bypass authentication and gain unauthorized access. There is no workaround — only the patch.

How the Attack Worked

Google Threat Intelligence Group and Mandiant published their technical analysis on November 20, attributing the intrusion to ARMORY CASTLE, a group previously tracked as UNC5221. The attack chain began somewhere else entirely: a zero-day in BeyondTrust Remote Support, tracked as CVE-2026-102764, which CISA added to its Known Exploited Vulnerabilities catalog on October 16.

From the BeyondTrust appliance, the attackers moved to an internal Linux system that had no endpoint detection and response agent installed, then scanned the network for VMware services, including TCP port 2012. That is where the new vCenter flaw came in. According to Mandiant, the flaw leaks a Secure Remote Password session key — the secret produced during the directory service’s password-based login handshake — over its RPC interface. With that key, an unauthenticated attacker can create an authenticated session as administrator@vsphere.local, the most powerful account in a vCenter deployment.

The group then deployed a custom Go-based tool Mandiant calls BONESAW. It copied and parsed vCenter’s directory database, stole the SAML signing key vCenter uses to vouch for logins, and created a new single sign-on administrator account. A second tool, SAWSNAKE, used the stolen signing material to forge SAML tokens — the “Golden SAML” technique that lets an attacker mint valid credentials at will. The attackers also enabled SSH on the vCenter appliance, took its master key and PostgreSQL database credentials, and pulled Active Directory database files straight from the virtual disks of guest virtual machines.

For persistence, Mandiant reports the group planted BEARBONES, a backdoored Dropbear SSH server that logs passwords; LAZYBONES, a Slack-controlled backdoor seen in an earlier ARMORY CASTLE intrusion; and two JSP web shells, SLIMSAVAGE and CAGEMATCH. Mandiant has not named the victim organization.

The Patch — and Its Limits

Broadcom’s fixes are vCenter 9.1.1.0200, 9.0.2.0200, and 8.0 Update 3m, plus Cloud Foundation 5.2.5. The flaw affects vCenter 8.0, 9.0, and 9.1, along with the vCenter builds inside VMware Cloud Foundation, vSphere Foundation, and the Telco Cloud Platform and Telco Cloud Infrastructure products. Older versions are not cleared: Broadcom says vSphere 6.5 and 6.7 should be presumed affected, and vSphere 7.0 — which left general support in October 2025 — can get a fix only under an extended support contract.

In an FAQ published with the advisory, Broadcom says the issue “qualifies under ITIL methodologies as an emergency change” and urges organizations to consult their security staff immediately on timing. The updates are cumulative and cannot be installed through vCenter Quick Patch. Virtual machines keep running while vCenter installs the update, though management access drops briefly.

The same advisory fixes four lower-severity flaws, rated 6.7 to 8.1: a SQL injection and a command injection in SDDC Manager, a privilege escalation to root on the SDDC Manager appliance, and a SAML token signature bypass in VMware Tools for Windows. Each needs an already authenticated or privileged actor. ESX itself is not affected, and none of the five flaws lets code run on an ESX host from inside a virtual machine, according to the advisory FAQ.

Broadcom also published a second critical advisory the same day, VMSA-2026-0010, for an Apache HTTP Server flaw bundled in Aria Operations and related products. As of November 20, those products have no patch — only a workaround that turns off HTTP/2.

This Is the Second Time This Year

CVE-2026-123890 is the second critical authentication bypass in the VMware Directory Service this year. The earlier set, patched on July 29, included CVE-2026-59309, another 9.8-rated bypass in the same component, alongside a directory-traversal bug, CVE-2026-59310. Attacks on that traversal flaw began five days after disclosure, German incident response firm QUIRSO assessed in August, compromising an estimated 361 IP addresses in 47 countries and deploying Babuk-derived ransomware on ESXi hosts.

The pattern is the warning. Edge and management appliances keep producing critical flaws, and the groups watching them move fast — sometimes before the patch exists at all.

What to Do Today

Patch vCenter immediately, treating this as an emergency change. But patching alone is not enough for anyone who may have been exposed during the two-plus months the flaw was a live zero-day. Hunt for rogue single sign-on administrator accounts, check for unexpected SAML signing key use, and review vCenter and directory service logs back to at least early September. Rotate the SAML signing keys and vCenter credentials, and segment vCenter so it is reachable only from trusted management networks. If any of the BONESAW, SAWSNAKE, BEARBONES, LAZYBONES, SLIMSAVAGE, or CAGEMATCH indicators appear, treat it as a full incident — the access these tools provide survives a patch.

The Bottom Line

A 9.8-rated authentication bypass in the console that runs the data center sat unpatched while a state-linked espionage group used it to forge its own administrator access for more than two months. The patch is out now, and there is no workaround, so the only question left is how fast organizations apply it — and whether they check for the intruders who may already be inside.

Sources: SecurityWeek; The Hacker News; Google Threat Intelligence Group and Mandiant; Broadcom advisory VMSA-2026-0009; Cybersecurity News; Cyber Kendra.

Edited by Muse @QUE.COM
Website: https://QUE.COM Intelligence
Sponsored by: https://MAJ.COM AI Autonomous
Never miss a customer call again — MAJ.COM’s AI receptionist answers every call, texts customers back instantly, and books the appointment for you. See how it works at https://MAJ.COM


Discover more from QUE.com

Subscribe to get the latest posts sent to your email.

Leave a Reply

Connect with

Discover more from QUE.com

Subscribe now to keep reading and get access to the full archive.

Continue reading