Cybersecurity 5 min read

CISA Lists a VMware vCenter Bypass Google Says Was Exploited From Early September, Before Any Patch

The US cyber agency added CVE-2026-123890 on 20 November, a day after Broadcom's fix. Mandiant says the attackers used it on a server already patched for July's vCenter bypass.

Priya Nair
Data, AI Governance & Policy Analyst
Published 21 Nov 2026, 4:48 PM (SGT)
Share:
An engineer works on the cabling of a server rack in a dark equipment room An engineer works on the cabling of a server rack in a dark equipment room Photo by This_is_Engineering on Pixabay
Advertisement

21 NOV 2026 — The US Cybersecurity and Infrastructure Security Agency (CISA) added an authentication bypass in VMware vCenter to its catalogue of exploited vulnerabilities on 20 November, one day after Broadcom published the fix. US federal civilian agencies have until 23 November to deal with it, and CISA has flagged the entry under its forensic triage requirements.

The flaw, CVE-2026-123890, was not new to the attackers. Google's Mandiant, which reported it to Broadcom, says a group it calls ARMORY CASTLE used it in early September, at least ten weeks before any patch existed. Google describes the group as a suspected China-nexus actor. That attribution is Google's assessment.

What the bug gives an attacker

vCenter is the console that runs a VMware estate. It configures the hypervisor hosts, holds the single sign-on directory and controls every virtual machine under it. Broadcom's advisory VMSA-2026-0009 scores the flaw 9.8 out of 10 and says anyone with network access to vCenter can use it to bypass authentication. It lists no workaround.

Google's report is more specific. The weakness sits in the VMware Directory Service remote procedure call interface, where predictable timestamps let an attacker recover a session key without a password. That yields a built-in administrator session. Mandiant says the group's tool, which it named BONESAW, used that session to create a new single sign-on administrator account and copy out the directory database. A second tool then used keys from that database to forge sign-in tokens, which Google says can bypass multi-factor authentication and impersonate any user.

The dates, in order

DateEventSource
13 Jul 2026Build timestamp in the recovered BONESAW binaryGoogle
29 Jul 2026Broadcom discloses CVE-2026-59309, a different directory-service bypassBroadcom, Google
Early Sep 2026BONESAW run against a vCenter server already patched for CVE-2026-59309Google
15 Oct 2026Google reports the same group exploiting a BeyondTrust zero-dayGoogle
19 Nov 2026Broadcom publishes VMSA-2026-0009 with fixesBroadcom
20 Nov 2026CISA lists CVE-2026-123890, due 23 NovemberCISA

For defenders, two rows stand out. The server BONESAW hit in September was already patched for July's flaw, which we covered in August. Broadcom's own questions-and-answers page calls the new bug "a new and distinct issue". Patching promptly in July was not enough for that team. Mandiant says it has evidence the group knew of the newer bug before July's disclosure. The tool's build timestamp falls 16 days before it, though Mandiant notes such metadata can be altered.

Advertisement

How the attackers reached vCenter

The intrusion Google describes did not start at vCenter. It started at a BeyondTrust Remote Support appliance, through the zero-day we reported in October. From there the group moved to an internal Linux appliance with no endpoint detection software, made itself root, and scanned for VMware services. One port it looked for, 2012, carries the single sign-on interface that BONESAW attacks. Google lists five new malware families and utilities from the campaign, but does not say how many organisations were hit.

That path is why the network-access condition is less reassuring than it sounds. vCenter is rarely on the open internet, but this attacker reached it from inside, through another appliance it had already taken.

Who has a fix, and who does not

Broadcom lists fixed versions for each supported line: 9.1.1.0200, 9.0.2.0200, 8.0 U3m, and 5.2.5 for VMware Cloud Foundation 5.x. For vCenter 7.0, the response matrix says only to contact Broadcom support if you have an extended support contract. vSphere 7 reached the end of general support on 2 October 2025, by Broadcom's account, so there is no public patch for it. Google says BONESAW achieves full compromise against vCenter 7.x and 8.x appliances. By our reading, the older of the two lines the tool targets is the one without a public fix.

There is also an upgrade catch. Broadcom says vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1, and customers mid-upgrade should wait for 9.1.2 or move vCenter to 9.1.1 first. The same advisory patches three flaws in SDDC Manager and one in VMware Tools for Windows. ESX hosts are not affected, Broadcom says.

CISA also added three other entries on 20 November: Apache Roller, Cisco Expressway and SAP NetWeaver, all with the same 23 November deadline. All but SAP carry the forensic flag. Google's report includes indicators and hardening steps for vCenter, including restricting which internal hosts can reach its management ports.

Advertisement
Priya Nair
Data, AI Governance & Policy Analyst

Priya Nair covers AI governance, data protection, privacy, and digital trust topics for RECATOOLS.

View author profile → · Editorial policy

About this byline Priya Nair is a RECATOOLS editorial persona for AI governance, privacy, and digital trust coverage. Articles are produced and reviewed under RECATOOLS editorial supervision.

Corrections policy

Advertisement