Security

CISA orders federal agencies to patch critical VMware vCenter flaw by November 23

A maximum severity authentication bypass in VMware vCenter stayed open for more than two months while a suspected Chinese espionage crew forged login tokens and pulled directory databases.

T
By TechQuire Daily Staff TechQuire Daily Staff
November 22, 2026 / 7 min read

Federal civilian agencies in the United States have until November 23, 2026 to close a maximum-severity authentication bypass in VMware vCenter, after the Cybersecurity and Infrastructure Security Agency added the flaw to its Known Exploited Vulnerabilities catalog on November 20, 2026. The bug is tracked as CVE-2026-123890 and carries a CVSS score of 9.8. The remediation order sits under Binding Operational Directive 26-04 and marks the flaw as an emergency, not a routine monthly patch.

vCenter is the control plane for VMware environments: administrators use it to manage ESXi hosts, provision and migrate virtual machines, and broker single sign-on for the wider stack. An attacker who holds an administrative vCenter session does not need to break into each hypervisor individually. From that position they can execute commands, move workloads, and reach the directory service that stores the material used to sign login tokens.

SecurityWeek reported on November 19, 2026 that a China-linked espionage group had exploited the vCenter zero-day for more than two months before Broadcom released a patch that day. Mandiant, which reported the bug to Broadcom, linked the activity to Armory Castle, a suspected Chinese threat actor formerly tracked as UNC5221 and also known as Warp Panda. According to the researchers, the group first gained access through CVE-2026-102764, a recently patched BeyondTrust Remote Support zero-day rated 9.3, then pivoted to Linux appliances on the internal network before targeting vCenter in early September 2026.

Broadcom shipped fixes in vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, with VCF 5.2.5 also listed as a fixed release. The vendor advisory resolves four additional flaws in SDDC Manager and VMware Tools but does not mention exploitation in the wild. The omission left the public record to Google's researchers, and it left defenders with a second question: whether the flaw had already been used against them.

Key Facts

Google Threat Intelligence Group and Mandiant described the bug as an unauthenticated Secure Remote Password (SRP-6a) session key disclosure vulnerability over DCE/RPC. Successful exploitation produces a remote authentication bypass that creates a session established as [email protected]. With that session, an attacker can execute arbitrary commands and acquire files, including the data.mdb database, through the vCenter Server Directory Service (vmdird) RPC interface known as vmdirdbcp.

The tooling is purpose-built. Mandiant said Armory Castle used BONESAW, a Golang utility written for remote exploitation of this specific flaw, to exfiltrate the Lightning Memory-Mapped Database, hijack the SAML Security Token Service and create a Single Sign-On administrator account. A second utility, SAWSNAKE, pulls signing keys out of that database and forges SAML login tokens. Help Net Security reported on November 20, 2026 that this capability lets the group forge authentication tokens, bypass multifactor authentication and impersonate any user in the environment. Token forgery outlives a password reset, because trust lives in the identity provider rather than in one account.

Cybersecurity Dive reported on November 19, 2026 that the attackers also moved to an ESXi host, pulled the Active Directory database and registry hives off a Windows virtual machine's disk, archived the files and moved them to the compromised BeyondTrust appliance, from which the data was likely exfiltrated. Mandiant counted five newly deployed malware families and utilities in the campaign: the SLIMSAVAGE and CAGEMATCH webshells, the BEARBONES backdoor, BONESAW and SAWSNAKE, alongside the previously seen LAZYBONES backdoor. SLIMSAVAGE was dropped as ActiveSer.jsp and authenticated with the hard-coded secret pwd=123. CAGEMATCH staged uploaded files into /tmp, and the group escalated to root by setting SUID permissions on /bin/env with gdb.

Reconnaissance was deliberate. After moving laterally from the BeyondTrust appliance, the intruders scanned internal networks with nmap for VMware-specific ports 9080, 5480 and 2012, the last of which serves as the vCenter SSO control RPC interface. Google said it found evidence that Armory Castle knew about CVE-2026-123890 before July 29, 2026, when a different vCenter authentication bypass, CVE-2026-59309, was disclosed, and that BONESAW was used against a vCenter server already patched for that earlier flaw. Charles Carmakal, chief technology officer at Mandiant Consulting, said the exploit tool was first discovered in July.

The Hacker News reported on November 21, 2026 that CISA added four flaws to the catalog that Friday, covering Apache Roller, Cisco Expressway, SAP NetWeaver and VMware vCenter. The Apache Roller entry, CVE-2026-129448, is a 9.8 deserialization flaw allowing unauthenticated remote code execution through the XML-RPC endpoint and was fixed in November 2026. Cisco Expressway's CVE-2026-76466 is a 9.8 hard-coded credential issue fixed in October 2026. SAP NetWeaver Enterprise Portal's CVE-2025-42884 is a 6.5 query-logic injection fixed in November 2025. Three of the four carry the maximum 9.8 score, and LavX News reported on November 21, 2026 that agencies were told to patch all four by November 23 under BOD 26-04.

Analysis

The most striking fact in the disclosure is not the CVSS score. It is the gap between knowledge and remediation. The exploit tool existed in July, the intrusion began in early September, the patch arrived on November 19, and the federal deadline lands on November 23. Four days of patching follows more than two months of confirmed exploitation. What this really means is that the catalog listing is less a warning about a future risk than a retroactive admission that a known, weaponized flaw sat open on the most sensitive layer of enterprise infrastructure for a full quarter.

The chain also reframes how defenders should think about management appliances. BeyondTrust Remote Support was the entry point, but the group chose not to stop at a single compromised appliance. It hunted for Linux boxes without endpoint detection and response tooling, then for VMware management interfaces by port. Every hop was a trust boundary that had been granted broad access and monitored thinly. The bigger picture here is that identity infrastructure and virtualization management have become the preferred terrain for espionage crews, because both concentrate privilege and both are frequently exempted from the endpoint controls applied to user laptops.

Attribution carries its own weight. Google and Mandiant tied the campaign to Armory Castle, a name change from UNC5221, and described two zero-days and three sets of tailored malware as evidence of deep platform expertise and substantial resource backing. Kelli Vanderlee, a senior analyst at GTIG, said a small number of organizations had been confirmed compromised but that additional targets had likely been affected. Confirmed victims in an espionage campaign are usually the ones with the telemetry to notice, not the full population.

There is also a version problem that no directive solves. BONESAW works against 7.x and 8.x, but there is no public patch for 7.0, which left general support in October 2025. An agency that follows the letter of a four day order may still be running an estate it cannot fully fix, which turns a compliance exercise into an architecture problem.

Why It Matters

The practical consequence is that a patched vCenter is not automatically a clean vCenter. Mandiant's own advice, echoed by Carmakal in a LinkedIn post, was for organizations to both apply the patches and examine their systems for evidence of compromise. An SSO administrator account created by an intruder, a forged SAML token, or an unexpected data.mdb export will survive the installation of a fixed build. Patching closes the door; it does not remove whoever is already inside.

The blast radius extends beyond a single agency. vCenter governs the virtual machines that run domain controllers, databases and backups. The reported theft of vCenter's master encryption key and database credentials, plus the extraction of an Active Directory database and registry hives from a guest VM, is the kind of material that supports follow-on access for years. That is why the catalog entry matters to private sector defenders too, even though the November 23 deadline binds only federal civilian executive branch agencies.

The same week's other KEV entries sharpen the point. Apache Roller, Cisco Expressway and SAP NetWeaver join vCenter in a single batch, and each offers an unauthenticated path to code execution, root access, information disclosure or unauthorized system access. Attackers are not choosing between perimeter and core. They are walking the seam between them, and management planes are where that seam is thinnest.

Next Up

Expect the forensic work to outlast the patch cycle. Organizations should verify patch status on internet-facing systems first, then on clustered devices, database services and management planes, and should review logs for unexpected authentication, JNDI lookups, XML-RPC requests and database commands. Broadcom's advisory resolves the SDDC Manager and VMware Tools issues as well, so a partial upgrade that fixes only vCenter may leave adjacent components exposed.

The longer question is whether the exploitation timeline forces a change in how zero-days in management appliances are disclosed and prioritized. Google published its technical analysis on the same day VMware disclosed the flaw, with seven Mandiant and GTIG authors attached to the write-up. The next disclosure of this kind will be judged against that standard, and against how quickly the four day deadline translates into verified, not merely scheduled, remediation.

Tagged

Comments (0)

No comments yet. Be the first to share your thoughts.