· 7 min read · LNX Inc.

vCenter zero-day was exploited two months before its fix

Broadcom fixes vCenter flaw CVE-2026-123890, exploited since September by the BeyondTrust intruders. Also Drupal, ASUS, FastUnlock and F5 BIG-IP.

Two analysts in a dim operations room before dawn, one pointing at a wall display of an incident timeline with three red markers

Broadcom has patched a vCenter Server flaw that Mandiant reported after investigating a real intrusion. CVE-2026-123890 lets anyone who can reach vCenter on the network log in as administrator@vsphere.local without a password. Google's Threat Intelligence Group says a suspected China-nexus espionage group used it in early September 2026, more than two months before Thursday, November 19, when the fix shipped. This Friday, November 20, it is the one job that should not wait for the weekend.

Update: the BeyondTrust intruders went on to vCenter

This is the same campaign the November 2 briefing covered. The group, ARMORY CASTLE (formerly UNC5221), first broke into a self-hosted BeyondTrust Remote Support appliance through CVE-2026-102764, patched in BT26-05. Google's new write-up, published November 19, follows what happened next. From the Remote Support appliance and an internal Linux appliance, the group scanned for VMware ports, then took over vCenter, then the ESXi hosts underneath it.

So the remote-support box was the way in, and the hypervisor was the target. For an MSP, that is the pattern to worry about: one internet-facing support tool, then the whole virtual estate.

A predictable session key opens the directory service

Broadcom's advisory, VMSA-2026-0009, rates CVE-2026-123890 at 9.8 and lists no workaround. It credits Mandiant with the report. Google describes the bug in the vCenter directory service's remote procedure call interface, on TCP port 2012. Predictable identifiers in its password handshake let an attacker recover the session key without knowing any password. The result is an authenticated session as the built-in vSphere administrator.

Google says the group's tool, BONESAW, used that session to copy the directory database, steal the SAML token-signing key, create a hidden single sign-on admin and grant it Global Administrator rights. Google says BONESAW works against vCenter 7.x and 8.x appliances. One detail matters for anyone who patched promptly in the summer. The September attack hit a vCenter that was already patched for an earlier, similar flaw, CVE-2026-59309.

How the intrusion unfolded

DateWhat happened
July 13, 2026Build timestamp in the BONESAW binary (Google notes this can be faked)
July 29, 2026CVE-2026-59309, a related vCenter directory flaw, is disclosed
Early September 2026ARMORY CASTLE runs BONESAW against a vCenter already patched for CVE-2026-59309
October 15, 2026BeyondTrust discloses CVE-2026-102764, the group's way in
November 19, 2026Broadcom publishes VMSA-2026-0009; Google publishes its analysis
November 20, 2026Broadcom updates the advisory to 0009.1 to clarify affected VMware Tools versions

CISA had not added CVE-2026-123890 to its exploited list as of its November 18 catalog. That is a lag, not a verdict; Mandiant's forensic findings are the exploitation evidence.

What the attackers did once inside

Google's account is detailed. The steps that leave traces an MSP can check for:

  • Web shells first. A web shell named ActiveSer.jsp on an internal Linux appliance, then a second, u.jsp.
  • Tools staged in /tmp. BONESAW at /tmp/123, a SAML token forger at /tmp/sss (deleted after use), and a backdoored SSH server at /tmp/dbr listening on TCP 53 and 33992.
  • A new local vCenter admin. The group created an account named sps-<something>@vsphere.local.
  • SSH switched on, then off. It enabled SSH on vCenter through the appliance management API, a PUT to /rest/appliance/access/ssh. It turned SSH off again after taking the vCenter master key and database credentials.
  • ESXi as root. It added its own key to root's authorized_keys, made a hidden .a folder on a datastore, and read Active Directory and registry files straight out of Windows VM disks. That last step means a domain controller VM can lose its password database without any sign inside Windows.
  • Persistence. A backdoor at /usr/bin/vmtoolscs, named to look like VMware Tools, run by a systemd service that restarts every 50 minutes. It takes commands through Slack.

Who is exposed

Any client with on-premises vSphere and a vCenter appliance. That means professional offices, schools, clinics and manufacturers with a small cluster, as well as anyone you host on your own vSphere stack. The flaw needs only network access to vCenter, not internet exposure. Google's case shows why that is little comfort: the attackers reached vCenter from another compromised box inside the network.

ESXi itself is not affected by this advisory, per Broadcom's Q&A. vSphere 7 is affected but reached end of general support on October 2, 2025. Broadcom lists no public fix for it, only "Contact Broadcom Support" for customers with extended support.

What to do

  1. Patch vCenter today. Fixed versions are 8.0 U3m, 9.0.2.0200 and 9.1.1.0200. VCF 5.x customers apply vCenter 8.0 U3m through Broadcom's KB 88287 and move SDDC Manager to 5.2.5. Broadcom's Q&A calls this an emergency change. Updating vCenter does not stop running VMs.
  2. Plan around vSphere 7. Without an extended support contract there is no fix. Cut network access to vCenter down to admin workstations while you schedule the upgrade.
  3. Restrict who can reach vCenter. Allow only named admin hosts to reach ports 443, 5480, 2012 and 22. Google warns that the built-in appliance firewall is managed through the same interface the attackers abused. It recommends Mandiant's VCSA hardening tool, including an outbound block on the appliance.
  4. Hunt before you close the ticket. Patching does not remove an admin account that already exists. Review vCenter SSO users for accounts nobody created. Check vCenter logs for SSH being enabled through the management API. Look for the files below on vCenter and other Linux appliances. On ESXi, check root's authorized_keys and look for hidden folders on datastores.
  5. Update VMware Tools on Windows guests. The same advisory fixes CVE-2026-123894 in VMware Tools for Windows: 13.1.5.0 for 13.x and 12.5.5 for 12.x. It is rated 6.7 and only affects guests set up with guest alias mapping. Fold it into normal patching.
  6. Close the front door too. If a client still runs self-hosted BeyondTrust Remote Support or Privileged Remote Access, confirm the BT26-05 patch is on it.

Indicators

Copied from Google's report. Google lists the IP addresses as a suspected relay network of compromised third-party routers and firewalls, so expect them to change.

TypeValueNote
FileActiveSer.jspSLIMSAVAGE web shell
Fileu.jspCAGEMATCH web shell
File/tmp/123BONESAW, vCenter exploit tool
File/tmp/sssSAWSNAKE, SAML forger
File/tmp/dbrBEARBONES, backdoored SSH server
File/usr/bin/vmtoolscsLAZYBONES, Slack backdoor
File/tmp/123.keySSH key used to reach ESXi
SSH bannerSSH-2.0-pulsesecure_23345On relay devices, high ports
Accountsps-<REDACTED>@vsphere.localLocal vCenter admin
API callPUT /rest/appliance/access/sshSSH enabled through the management API
IP103.147.251.5, 103.190.38.3, 118.174.128.34, 118.174.128.36, 118.174.128.38Relay network
IP176.9.89.66, 185.71.15.109, 220.121.128.41, 222.108.77.44, 61.216.56.127, 81.45.89.43Relay network

Google's post also carries YARA rules for each malware family.

Also today

Drupal fixes an installer flaw that can hand over the site. SA-CORE-2026-017, published November 18, covers CVE-2026-132165. Under specific conditions, an anonymous visitor can use install.php to try to reinstall Drupal, which can lead to site takeover or code execution. Drupal rates it Critical (18 of 25), with high attack complexity, and marks a proof of concept as existing. No exploitation is reported. Update to 11.4.13, 11.3.22 or 10.6.22. If that has to wait, lock down the installer as Drupal's advisory describes, and make sure the web server cannot write to settings.php. Sites on Drupal 10.5, 11.2 or older get no fix. Agencies and nonprofits that host Drupal sites for clients should check their whole list.

ASUS fleet management has a 10.0 flaw. ASUS Control Center Express manages ASUS business desktops and laptops. Its security bulletin fixes three critical flaws in versions before 1.7.29. The worst, CVE-2026-114202, is a hard-coded key rated 10.0 under CVSS 4.0 that needs no login. ASUS says the flaws could give a remote user admin access to the console and the clients it manages. No exploitation is reported. Install 1.7.29, then push the new agent through "Client Agent Updater" and confirm the agent version on each device.

FastUnlock claims a BitLocker bypass on fully patched Windows 11. A researcher who has published several Windows zero-days, Chaotic Eclipse, released FastUnlock on November 19, as reported by Security Affairs. The claim is code execution from the lock screen through Narrator, with physical access, on Windows 11 26H2 with November's patches. It is said to need at least one account on the machine linked to a Microsoft account. No CVE, Microsoft response or independent confirmation exists yet. The risk is to lost or stolen laptops. Make sure your lost-device process includes revoking the user's sessions and resetting their password, and watch for Microsoft's response.

F5 ships emergency BIG-IP fixes. F5 released out-of-band hotfixes for five critical flaws in BIG-IP APM and iRules that allow unauthenticated code execution, and one high-rated APM SAML denial-of-service bug, as reported by BleepingComputer. F5 has not flagged any as exploited and lists no mitigation. Clients with a BIG-IP doing remote access should get the hotfix from F5's advisories, starting with K000163946.

Sources

Tell us what's in front of you.

A drawing set, a failing switch, an audit deadline, or a hunch that IT costs too much. We'll tell you who picks it up and what it takes.