Skip to content
Breach Index · running record

VMware vulnerabilities in 2026: vCenter CVE-2026-123890 (not a breach of VMware or Broadcom)

VMware vCenter is the management server for vSphere, so whoever controls it controls the virtual machines and ESXi hosts beneath it. Broadcom owns VMware. This page tracks the critical vCenter flaw fixed in November 2026 and keeps Broadcom's advisory apart from what Google and Mandiant say about its exploitation.

Short answer

Was VMware hacked?

No, CVE-2026-123890 is not a breach of VMware or Broadcom: nothing reported shows an intrusion into their own systems. It is an authentication bypass in the VMware Directory Service in vCenter, rated CVSS 3.1 9.8, which Broadcom fixed on 19 November 2026 in VMSA-2026-0009 (vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, and VMware Cloud Foundation 5.2.5), with no workaround.

Google Threat Intelligence Group and Mandiant say a suspected PRC-nexus espionage actor they call ARMORY CASTLE (formerly UNC5221) exploited it on a customer network in early September 2026, more than two months before the fix, and went on to reach ESXi hosts. Broadcom credits Mandiant with the report but does not itself state exploitation. It was not in CISA KEV as of 20 November 2026.

Timeline at a glance

  1. Early Sep 2026ARMORY CASTLE exploits the vCenter flaw as a zero-day with a custom tool, BONESAW, per forensic evidence. (Google / Mandiant)Reported
  2. 19 Nov 2026Broadcom publishes VMSA-2026-0009: CVE-2026-123890, CVSS 9.8, fixed vCenter builds, no workaround. (Broadcom)Not a breach
  3. 19 Nov 2026Google and Mandiant publish their report on ARMORY CASTLE's vCenter and ESXi intrusion. (Google / Mandiant)Reported
  4. 20 Nov 2026VMSA-2026-0009.1 clarifies VMware Tools versions; CVE-2026-123890 not in CISA KEV (catalog 2026.11.18). (Broadcom)Not a breach

Last updated 20 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

VMware (Broadcom) incident timeline, in detail

Confirmed = acknowledged by VMware (Broadcom), a regulator filing or a court. Reported = credible reporting VMware (Broadcom) has not fully confirmed. Unverified claim = an attacker or leak-site claim.

Nov 2026Not a breachProduct vulnerability (pre-authentication), exploited per Google

vCenter CVE-2026-123890: authentication bypass exploited as a zero-day, per Google

What happened. Broadcom VMSA-2026-0009: an authentication bypass in the VMware Directory Service; a network attacker with access to vCenter may bypass authentication and gain unauthorized access (CVSS 3.1 9.8). Fixed in vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m and VCF 5.2.5; Telco Cloud Platform and Telco Cloud Infrastructure via KB463116; vCenter 7.0 is affected and extended-support customers must contact Broadcom. No workaround. Broadcom's FAQ says ESX is not affected. The same advisory fixes four lower-rated flaws in SDDC Manager and VMware Tools for Windows.

Impact. Google says ARMORY CASTLE used the flaw in early September 2026 to steal vCenter's token-signing key, forge administrator logins and create an SSO administrator, then took database credentials and the master encryption key, deployed webshells and backdoors, and reached ESXi hosts. Google calls the actor suspected PRC-nexus; the victim is not named. Broadcom does not state exploitation, and the flaw was not in CISA KEV as of 20 November.

Sources: Broadcom VMSA-2026-0009 · Broadcom FAQ · CVE record · Google / Mandiant

Where the reports disagree

  • Exploitation: Google and Mandiant say the flaw was exploited from early September 2026; Broadcom's advisory and FAQ do not address exploitation and say only that it was privately reported.
  • Affected versions: the advisory and CVE record list fixes for vCenter 9.1, 9.0 and 8.0 and VCF 5.x; Broadcom's FAQ says vSphere 7 is also affected; Google says BONESAW targets vCenter 7.x and 8.x.
  • Attribution: Google calls ARMORY CASTLE a suspected PRC-nexus actor; some outlets report it as confirmed or add other aliases that Google's report does not use. We follow Google.

The pattern across the record

Management planes are the prize

Like PAN-OS management interfaces and remote-support appliances, vCenter holds the keys to everything beneath it. Google says the group entered through a BeyondTrust Remote Support zero-day and moved to vCenter and ESXi.

Vulnerabilities are not breaches

Nothing reported shows an intrusion at VMware or Broadcom. The exposure is to every organisation running an unpatched vCenter that attackers can reach.

What it means for VMware (Broadcom) customers — and what to do

If you run vCenter, VMware Cloud Foundation or vSphere Foundation, the questions are whether every vCenter is patched, who can reach it, and whether anyone got in before you patched.

  1. 1.Patch vCenter now

    Move to 9.1.1.0200, 9.0.2.0200, 8.0 U3m or VCF 5.2.5. There is no workaround; vCenter 7.0 extended-support customers must contact Broadcom.

    vCenter CVE-2026-123890: what to do
  2. 2.Hunt before you trust it

    Treat an unpatched vCenter reachable from user or server networks as possibly compromised. Use Google's published detections; check for unexpected SSO admins, SSH enablement and root SSH keys on ESXi.

    Google / Mandiant report
  3. 3.Restrict and rotate

    Keep vCenter on an admin network, then replace the token-signing certificate and rotate the credentials vCenter holds. Record any unpatched 7.0 with an owner and a date.

    Risk register
Take this with you
Incident timeline · What VMware (Broadcom) customers should do · Sources

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed 20 November 2026.

  1. 1.VMSA-2026-0009: VMware vCenter, Tools, and SDDC Manager updates address multiple vulnerabilities — Broadcom, 19 Nov 2026
  2. 2.VMSA-2026-0009 questions and answers — Broadcom (GitHub vmware), 19 Nov 2026
  3. 3.CVE-2026-123890 (CNA VMware) — CVE.org, 19 Nov 2026
  4. 4.ARMORY CASTLE Exploits vSphere — Google Threat Intelligence Group / Mandiant, 19 Nov 2026

Frequently asked questions

Was VMware hacked?

No breach of VMware or Broadcom is reported. CVE-2026-123890 is a vulnerability in vCenter, fixed on 19 November 2026 in VMSA-2026-0009.

Which vCenter versions fix CVE-2026-123890?

9.1.1.0200, 9.0.2.0200 and 8.0 U3m, and VMware Cloud Foundation 5.2.5. vCenter 7.0 is affected; extended-support customers must contact Broadcom.

Is CVE-2026-123890 exploited?

Google and Mandiant say ARMORY CASTLE, a suspected PRC-nexus actor, exploited it from early September 2026. Broadcom does not state exploitation, and it was not in CISA KEV as of 20 November 2026.

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by VMware (Broadcom). Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.