← gociux.comall insights

Vulnerability alert · 19 Nov 2026

vCenter CVE-2026-123890: authentication bypass reported exploited. Patch, then hunt

, Gociux · 19 Nov 2026 · 6 min read

TL;DR

If you run vCenter 8.0, 9.0 or 9.1 below the fixed builds, an attacker who can reach it on the network can log in as the SSO administrator without a password. Broadcom's fix shipped on 19 November 2026, with no workaround, and Broadcom itself calls it an emergency change. Mandiant reports the flaw was already used in targeted espionage before the fix. Patch today, then check whether someone got in first: rogue SSO admins, SSH switched on and off, and forged SAML tokens survive the patch.

What the vulnerability is

CVE-2026-123890 is an authentication bypass in the VMware Directory Service (vmdir), the identity store behind vCenter single sign-on. Mandiant's analysis, as summarised by SecurityOnline, says the RPC interface on TCP port 2012 discloses a Secure Remote Password session key. An attacker uses it to get an [email protected] session without the password (SecurityOnline). It is a different bug from July's vmdir flaw CVE-2026-59309: the attack tool worked against servers already patched for that one.

The same advisory, VMSA-2026-0009, fixes four lower-rated issues: SQL injection (CVE-2026-123891), command injection (CVE-2026-123892) and privilege escalation (CVE-2026-123893) in SDDC Manager, and a SAML signature bypass in VMware Tools for Windows (CVE-2026-123894). ESXi is not affected, nor are NSX, VCF Operations, VCF Automation, Workstation or Fusion (Broadcom VMSA-2026-0009 Q&A).

Fixed versions

One trap from Broadcom's FAQ: vCenter 8.0 U3m and 9.0.2.0200 block a later upgrade to VCF 9.1.1, so Broadcom advises going to VCF 9.1.2 when it ships. Don't let that delay the fix. Running VMs keep running while vCenter is updated.

Is it being exploited?

SecurityOnline reports that Mandiant and Google Threat Intelligence attribute in-the-wild exploitation to ARMORY CASTLE, a suspected China-nexus espionage group previously tracked as UNC5221. The exploitation dates to early September 2026, and the group's exploit tool BONESAW carries a July build timestamp. NHS England's cyber alert also describes it as a zero-day. Broadcom's advisory doesn't comment on exploitation, and The Hacker News, published earlier, said Broadcom had reported no attacks (The Hacker News). Treat it as exploited. Check the CVE lookup for when CISA adds it to KEV.

The reported intrusion shows what happens after the bypass. It started with ARMORY CASTLE's BeyondTrust Remote Support zero-day (CVE-2026-102764, in CISA KEV since 16 October). The group moved to an internal Linux appliance without EDR and scanned for port 2012. It used BONESAW to copy the directory database, steal the SAML signing key and create an SSO admin. It then forged SAML logins ("Golden SAML") to bypass MFA. Finally it enabled SSH on vCenter, took its master key and database credentials, and disabled SSH again.

What to do, in order

  1. Patch vCenter now to the build for your branch. Broadcom classifies it as an emergency change, so don't wait for the monthly window.
  2. Restrict port 2012 (and the vCenter management interfaces generally) to dedicated admin hosts and jump boxes. vCenter should never be reachable from user networks or from appliances like remote-support boxes.
  3. Hunt for prior compromise:
    • SSO users and groups: any administrator you didn't create, especially recent ones.
    • VAMI and appliance logs: SSH enabled and then disabled again.
    • SSH servers on high ports announcing SSH-2.0-pulsesecure_23345.
    • JSP files on the appliance that aren't part of vCenter.
  4. If anything looks wrong, rotate the STS signing certificate and all SSO credentials. Forged SAML tokens keep working after patching until the signing key changes. Treat Active Directory as exposed too: the attackers pulled AD database files from domain controller VM disks.
  5. Patch BeyondTrust Remote Support if you run it, and look at every internal appliance without EDR that can reach vCenter.
  6. Update SDDC Manager and VMware Tools for Windows in the same change, if you run VCF or rely on Tools' SAML features.

The compliance angle

vCenter controls every VM, including domain controllers and anything in PCI scope, so compromising it is equivalent to compromising the whole environment. For PCI DSS this is a critical vulnerability on a system that is in scope or connected to it, and the management network must be segmented from users. For NIS2 and DORA, a confirmed compromise of the virtualisation layer is very likely a significant incident; the incident clock calculates the reporting deadlines. Keep evidence of the patch date, the hunt you ran and what it found.

Questions

Which vCenter versions fix CVE-2026-123890?

vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, released on 19 November 2026; VCF 5.x customers apply 8.0 U3m with SDDC Manager 5.2.5. vCenter 7.0 and older are out of support and should be presumed affected.

Is ESXi affected by CVE-2026-123890?

No. Broadcom says ESX/ESXi is not affected by VMSA-2026-0009. The flaw is in vCenter's directory service, but an attacker who controls vCenter can still manage every ESXi host attached to it.

Is there a workaround for the vCenter authentication bypass?

Broadcom lists none, so patching is the fix. Restricting network access to vCenter, including TCP port 2012, to trusted management hosts reduces exposure while you schedule it.

Need help checking whether your vCenter was touched?

We patch and segment the management plane, hunt for rogue SSO admins and forged SAML activity, and help you rotate the identity keys safely, with the evidence your PCI DSS or NIS2 auditor will ask for.

Request a quote →

Sources

Developing story, last checked 19 Nov 2026 around 17:30 UTC. Broadcom's VMSA is the source of truth for fixed builds.