Skip to main content

vCenter Auth Bypass CVE-2026-123890: What Boards Should Ask About Virtualization Management

4 min read
CISO Daily
vCenter Auth Bypass CVE-2026-123890: What Boards Should Ask About Virtualization Management

The short version

Broadcom patched a critical authentication bypass in VMware vCenter on 19 November 2026 (advisory VMSA-2026-0009, CVE-2026-123890, CVSS 9.8 as scored by Broadcom). Google’s Threat Intelligence Group (GTIG) says a suspected China-nexus group, tracked as ARMORY CASTLE (formerly UNC5221), says forensic evidence shows exploitation in early September 2026. There is no workaround. Only patching fixes it.

vCenter is the console that controls an organization’s virtual servers. Whoever controls it can reach nearly everything running on top of it, which is why the flaw matters well beyond the infrastructure team.

What is reported

GTIG links this activity to its earlier reporting on a BeyondTrust Remote Support flaw (CVE-2026-102764, on the CISA Known Exploited Vulnerabilities list since 16 October). In the 19 November report, the actor moves laterally from the Remote Support device to a Linux appliance with no endpoint detection, then used the vCenter flaw to create its own administrator without credentials.

GTIG describes two custom tools. One creates a single sign-on administrator, copies the identity database and extracts the key that signs login tokens. The other forges login tokens using that key, a technique known as Golden SAML, which sidesteps multi-factor authentication. The actor also enabled remote shell access, took vCenter’s master key and database credentials, and pulled the domain’s password database from the disks of virtual machines.

Our assessment (not from GTIG or Broadcom): patching the hole does not remove an attacker who already holds the signing key, so organizations that were reachable should consider treating identity material as potentially stolen.

What is not established

  • Exploitation rests on GTIG’s reporting alone. There are no named victims.
  • Broadcom’s advisory does not say the flaw is being exploited.
  • CISA’s assessment lists exploitation as “none”, and as of the 18 November data the CVE was not on the Known Exploited list. Our assessment: that status can change quickly, and it should not be read as a clean bill of health.
  • We have not seen an independent technical confirmation of the attribution.

Who needs to act first

Per Rapid7 relaying Broadcom, this is an emergency change with no vCenter Quick Patch, and systems already patched for CVE-2026-59309 still need this update. The advisory covers five CVEs.

Fixed versions are vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, VMware Cloud Foundation 5.x in 5.2.5, and Telco Cloud under KB463116. vCenter 7.0 reached end of general support on 2 October 2025 and has no public fix unless you hold extended support. If any of your estate is on 7.0, that is a decision for leadership, not just IT: extend, migrate, or isolate.

Questions to ask this week

  1. Exposure. Is vCenter reachable from the internet or from any vendor remote-access path? Who confirmed it, and how?
  2. Version. Which vCenter versions do we run, and are any on 7.0?
  3. Patch date. When will each instance be patched, and who signs off on the maintenance window?
  4. Compromise assessment. If we were reachable since September, have we looked for new administrator accounts, unexpected SSH enablement and unusual token activity? Patching alone will not answer this.
  5. Credential reset (our recommendation). Are we prepared to rotate the signing certificate, vCenter service credentials and any domain credentials that could have been exposed?
  6. Entry points. Do we run BeyondTrust Remote Support, and did we patch CVE-2026-102764 when it was listed in October?
  7. Visibility. Do our management appliances run endpoint monitoring? The actor chose a host without it.

We covered the same pattern in When a VPN Flaw Becomes a Hypervisor Problem and Januscape: management planes are high-value, often lightly monitored, and the blast radius is the whole virtual estate.

Bottom line

Patch, then investigate. If you were exposed during the window, plan for compromise assessment and credential rotation as part of the same work, and tell the board now that the root cause is an upstream vendor flaw that we are managing, with the scope of exposure still being established.

Sources: GTIG reporting on ARMORY CASTLE; Broadcom VMSA-2026-0009; CISA KEV and SSVC data as of 18 November 2026; Rapid7 analysis of CVE-2026-123890.