Actively exploited CVSS 9.8 Security news

VMware vCenter CVE-2026-123890: critical authentication bypass exploited as a zero-day by a China-nexus group

On 19 November 2026 Broadcom published VMSA-2026-0009, fixing CVE-2026-123890, a critical flaw in VMware vCenter (CVSS 9.8) that lets an attacker with network access log in as the vSphere administrator without a password. Broadcom says nothing about attacks, but on the same day Google Threat Intelligence Group (GTIG) and Mandiant showed that ARMORY CASTLE, a suspected China-nexus group, was already exploiting it in early September 2026 – and used vCenter to reach data inside other virtual servers.

Kyberkit editorial team · · event date · reading time 4 minutes · For admins and analysts

Actively exploited: VMware vCenter, CVE-2026-123890, CVSS 9.8

Key points

  • Affected: vCenter 7.0, 8.0, 9.0 and 9.1 (also inside VCF, vSphere Foundation and Telco Cloud). Fixes: 9.1.1.0200, 9.0.2.0200, 8.0 U3m, VCF 5.2.5; 7.0 only through Broadcom extended support.
  • The bug: an authentication bypass in the VMware Directory Service – according to GTIG, predictable UUID generation in an RPC service on port 2012 leads to a login as administrator@vsphere.local.
  • Exploited: yes. GTIG attributes the attacks to ARMORY CASTLE (formerly UNC5221), which got in through BeyondTrust Remote Support and then used vCenter to raid ESXi hosts and domain controllers.
  • Broadcom lists no workaround. The same advisory also fixes SDDC Manager (CVE-2026-123891 to -123893) and VMware Tools for Windows (CVE-2026-123894).

Vulnerabilities: CVE-2026-123890

What happened

On 19 November 2026 Broadcom published VMSA-2026-0009, rated critical overall. The most serious of its five fixes is CVE-2026-123890 in VMware vCenter: an authentication bypass in the VMware Directory Service that an attacker with network access can exploit without credentials or user interaction (CVSS 3.1 9.8, vector AV:N/AC:L/PR:N/UI:N per NVD). Mandiant reported it. Broadcom lists no workaround and says nothing about exploitation.

The same day, however, Google Threat Intelligence Group and Mandiant published an analysis showing that the flaw was exploited as a zero-day by ARMORY CASTLE (formerly tracked as UNC5221), a suspected China-nexus espionage group. Its BONESAW tool used the bug in early September 2026. It follows GTIG's October report on the same group breaking into networks through a zero-day in BeyondTrust Remote Support (CVE-2026-102764).

Technical details

  • Component: the VMware Directory Service (vmdir) in vCenter, specifically a DCE/RPC service on TCP 2012.
  • Bug class: according to GTIG, the service discloses an SRP-6a session key without authentication because it relies on predictable timestamps in UUIDv1 identifiers. NVD classifies it as authentication bypass using an alternate path (CWE-288).
  • Preconditions: network access to vCenter. No authentication or user interaction.
  • Impact: login as administrator@vsphere.local, which means full control of vCenter and, through it, the ESXi hosts and virtual machines.
  • How the intrusions unfolded, per GTIG: from the compromised BeyondTrust appliance the attacker scanned vCenter ports (9080, 5480, 2012), planted the SLIMSAVAGE and CAGEMATCH web shells and used gdb to set the SUID bit on /bin/env. BONESAW then created an SSO admin account and took the data.mdb database holding the STS signing key, and SAWSNAKE forged SAML tokens ("Golden SAML") that bypassed MFA. The attacker enabled SSH through the VAMI API, stole the vCenter master encryption key and PostgreSQL credentials, and finally moved to ESXi, pulling data such as the Active Directory database (NTDS) out of virtual machine disks.
  • Persistence: the BEARBONES backdoor (modified Dropbear SSH on TCP 53 and 33992), the Slack-controlled LAZYBONES backdoor (systemd service /usr/bin/vmtoolscs) and an SSH key for root on ESXi.
ARMORY CASTLE attack on vSphere according to GTIG1. A BeyondTrust Remote Support zero-day gives the attacker internal network access; 2. vCenter port scan and the SLIMSAVAGE web shell on vCenter; 3. BONESAW exploits CVE-2026-123890 and creates an SSO admin account; 4. Signing key theft and Golden SAML bypass MFA; 5. SSH to ESXi and extraction of VM disks (NTDS, DNS)1A BeyondTrust Remote Support zero-daygives the attacker internal networkaccess2vCenter port scan and the SLIMSAVAGEweb shell on vCenter3BONESAW exploits CVE-2026-123890 andcreates an SSO admin account4Signing key theft and Golden SAMLbypass MFA5SSH to ESXi and extraction of VMdisks (NTDS, DNS)
Based on GTIG and Mandiant (19 Nov 2026)

Who is affected

columns: Product | Version | Status
row: vCenter | 9.1.x before 9.1.1.0200 | vulnerable
row: vCenter | 9.0.x before 9.0.2.0200 | vulnerable
row: vCenter | 8.0 before U3m | vulnerable
row: vCenter | 7.0 | vulnerable
row: vCenter | 9.1.1.0200 / 9.0.2.0200 / 8.0 U3m | fixed
row: VMware Cloud Foundation (vCenter) | 5.2.5 | fixed
  • vCenter 7.0 fixes are only available through Broadcom Support under an extended support contract. For Telco Cloud Platform and Telco Cloud Infrastructure, Broadcom points to KB463116.
  • The VMware FAQ advises assuming that unsupported vSphere 6.5 and 6.7 are vulnerable too.
  • Also in the advisory: SDDC Manager – SQL injection CVE-2026-123891 (8.1), command injection CVE-2026-123892 (7.2) and root privilege escalation CVE-2026-123893 (6.7), fixed in 9.1.1.0200, 9.0.2.0100 and 5.2.5; VMware Tools for Windows – SAML token signature bypass CVE-2026-123894 (6.7), fixed in 13.1.5.0 and 12.5.5.

How to tell if you were compromised

GTIG did not publish file hashes (the full set is in a VirusTotal collection for registered users). The write-up lists these indicators (defanged):

103.147.251[.]5
103.190.38[.]3
118.174.128[.]34
118.174.128[.]36
118.174.128[.]38
176.9.89[.]66
185.71.15[.]109
220.121.128[.]41
222.108.77[.]44
61.216.56[.]127
81.45.89[.]43
ActiveSer.jsp
u.jsp
/tmp/123
/tmp/sss
/tmp/dbr
/usr/bin/vmtoolscs
SSH banner: SSH-2.0-pulsesecure_23345
  1. On vCenter, look for the files above and other artifacts from the write-up: /tmp/gdb_file, /tmp/123.rar, /tmp/123.key, and a SUID bit on /bin/env (ls -l /bin/env).
  2. In vCenter logs, look for PUT /rest/appliance/access/ssh calls (SSH being enabled), unknown accounts in the vsphere.local domain and new machine accounts with admin rights.
  3. Watch for traffic to port 2012 from outside the management network.
  4. On ESXi, check root's authorized_keys, hidden .a directories on VMFS volumes, o.tar.gz archives, and listeners on TCP 53 and 33992.
  5. GTIG also published YARA rules (SLIMSAVAGE, CAGEMATCH, BONESAW, SAWSNAKE, BEARBONES, LAZYBONES). Pull indicators out of your own logs quickly with our IOC extractor.

What to do

  1. Upgrade vCenter now to 9.1.1.0200, 9.0.2.0200, 8.0 U3m or VCF 5.2.5. There is no workaround.
  2. Restrict network access to vCenter (ports 2012, 5480, 9080 and the web UI) to the management network. Mandiant offers the VCSA Hardening & Logging Tool with default-deny inbound and egress rules – test it before using it in production.
  3. Hunt for compromise even after patching – the attacks date back to September, long before the fix.
  4. If you find anything, treat the whole vSphere environment and the domain as compromised: the STS signing key, the vCenter master key and the password hashes in NTDS may be in the attacker's hands. Recovery means rotating STS certificates and account passwords and following your incident response plan.
  5. Patch BeyondTrust Remote Support too (fix BT26-05) and other edge devices – that is where the intrusion began.

Timeline

CVE-2026-123890 timeline in VMware vCenter29 Jul 2026: VMware fixes a different vmdir bug, CVE-2026-59309; early Sep 2026: BONESAW exploits CVE-2026-123890, even against vCenter with the July fix (GTIG); 15 Oct 2026: GTIG reports ARMORY CASTLE intrusions through BeyondTrust Remote Support; 19 Nov 2026: Broadcom publishes VMSA-2026-0009, NVD entry, GTIG releases its analysis and indicators29 Jul 2026VMware fixes a differentvmdir bug, CVE-2026-59309early Sep2026BONESAW exploitsCVE-2026-123890, even againstvCenter with the July fix(GTIG)15 Oct 2026GTIG reports ARMORY CASTLEintrusions throughBeyondTrust Remote Support19 Nov 2026Broadcom publishesVMSA-2026-0009, NVD entry,GTIG releases its analysisand indicators
Based on Broadcom, NVD and GTIG

FAQ

Broadcom doesn't mention exploitation. Who should I believe?

VMSA-2026-0009 simply says nothing about exploitation. Mandiant reported the bug to Broadcom, and the GTIG/Mandiant write-up of 19 Nov 2026 describes specific intrusions in which the BONESAW tool exploited it. Treat vCenter as an actively targeted system: patch, then look for signs of compromise.

Am I safe if vCenter isn't exposed to the internet?

Your risk is lower, but that isn't enough. In the intrusions GTIG describes, the attacker reached vCenter from inside the network, from a compromised BeyondTrust Remote Support appliance. Port 2012 and the vCenter management interfaces should only be reachable from a management network or jump hosts.

Is this the same flaw as CVE-2026-59309 from July?

No. CVE-2026-59309 was a different bug in the same component (vmdir, LDAP on ports 389/636). GTIG says BONESAW was run against a vCenter already patched for CVE-2026-59309, so the July fix does not protect against the new flaw.

Does this affect standalone ESXi without vCenter?

CVE-2026-123890 is a vCenter bug, and the advisory does not list standalone ESXi as affected. Do update VMware Tools in Windows guests, though, because of CVE-2026-123894.

Sources

  1. Broadcom - VMSA-2026-0009: VMware vCenter, Cloud Foundation, vSphere Foundation, Tools and Telco Cloud (19 Nov 2026)
  2. NVD - CVE-2026-123890
  3. Google Threat Intelligence Group and Mandiant - ARMORY CASTLE Exploits vSphere (19 Nov 2026)
  4. VMware - VMSA-2026-0009 FAQ (GitHub)
  5. Mandiant - VCSA Hardening & Logging Tool (GitHub)

Spotted a mistake? Let us know and we will correct it openly.