Skip to content
>_KernelBrief
Cybersecurity

VMware vCenter Zero-Day CVE-2026-123890 Was Exploited for Months: Who Is Affected and How to Patch

VMSA-2026-0009 fixes vCenter auth bypass CVE-2026-123890, exploited since September per Mandiant. Fixed builds, no workaround, and what to check.

By Published 6 min read
// SECURITY
Table of contents

Broadcom has patched CVE-2026-123890, a critical authentication bypass in VMware vCenter that Google's Mandiant says a suspected China-nexus espionage group exploited as a zero-day since at least early September 2026. The fix shipped on November 19 in VMSA-2026-0009, there is no workaround, and CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on November 20. If you run vCenter, standalone or inside VMware Cloud Foundation, update now and check for signs of earlier compromise.

What happened

On November 19, 2026, Broadcom published VMSA-2026-0009, a bundled advisory covering five vulnerabilities across vCenter, SDDC Manager and VMware Tools for Windows. Broadcom's Q&A puts the CVSS 3.1 scores in the range of 6.7 to 9.8. The most serious is CVE-2026-123890, an authentication bypass in the VMware Directory Service component of vCenter, rated 9.8.

Broadcom credits Mandiant with discovering the bug. The next day, Help Net Security reported on research from Mandiant and Google Threat Intelligence Group (GTIG) describing multiple intrusions in which the flaw was abused before any patch existed. On November 20, CISA added four exploited flaws to the KEV catalog, including the vCenter bug, which obliges US federal civilian agencies to remediate on a short deadline.

Broadcom also says CVE-2026-123890 is a new and distinct issue, not a bypass of the earlier vCenter authentication flaw CVE-2026-59309 fixed in July.

Confirmed facts vs. reported details

It helps to separate what the vendor states from what comes from threat-intelligence reporting.

Confirmed by Broadcom (VMSA-2026-0009):

  • CVE-2026-123890 is an authentication bypass in vCenter's directory service, rated critical.
  • The same advisory fixes CVE-2026-123891, -123892 and -123893 in SDDC Manager (SQL injection, authenticated command injection and local privilege escalation) and CVE-2026-123894, a SAML token signature bypass in VMware Tools for Windows that allows local privilege escalation inside a guest.
  • There are no workarounds. Disabling guest operations or removing VMware Tools does not count as a mitigation for CVE-2026-123894.
  • ESX, NSX, VCF Operations, VCF Automation, Workstation and Fusion are not affected.

Reported by Mandiant/GTIG (via Help Net Security):

  • Exploitation began no later than early September 2026, more than two months before the patch.
  • The activity is attributed to a group Google tracks as ARMORY CASTLE (formerly UNC5221), which Google assesses as a suspected China-nexus espionage actor. Attribution is an analytic judgment, not a vendor-confirmed fact.
  • Initial access in at least one intrusion came through a separate zero-day in BeyondTrust Remote Support (CVE-2026-102764).
  • After exploiting vCenter, the attackers created an SSO administrator account, copied the vCenter directory database, forged SAML tokens to impersonate users and get around MFA, and extracted Active Directory data from Windows virtual machine disks.
  • Mandiant observed five previously unseen malware families or tools and has published indicators and YARA rules in its report.

Note that Broadcom's advisory itself does not describe in-the-wild exploitation; the exploitation evidence comes from Mandiant/GTIG and from CISA's KEV listing.

Who is affected

  • vCenter 9.1.x, 9.0.x and 8.0, whether standalone or part of VMware Cloud Foundation, vSphere Foundation, or VMware Telco Cloud Platform/Infrastructure. Using Enhanced Linked Mode or not makes no difference.
  • vCenter 7.0 is affected but reached the end of general support on October 2, 2025; extended-support customers should go through Broadcom support. Broadcom advises treating 6.5 and 6.7 as affected.
  • SDDC Manager 9.1.x, 9.0.x and 5.x (for the three SDDC Manager CVEs).
  • VMware Tools for Windows 13.x, 12.x and 11.x (for CVE-2026-123894). Tools on other guest operating systems is not listed.

vCenter is an especially valuable target because whoever controls it controls the virtual infrastructure beneath it. As with the exploited Puppet Server flaw we covered this week, the risk is less about one server and more about everything that server manages.

Fixed versions

Broadcom's fixes are cumulative and also include the VMSA-2026-0008 fixes.

Product Branch First fixed release
vCenter 9.1.x 9.1.1.0200
vCenter 9.0.x 9.0.2.0200
vCenter 8.0 8.0 U3m
vCenter 7.0 Contact Broadcom (extended support)
SDDC Manager 9.1.x / 9.0.x / 5.x 9.1.1.0200 / 9.0.2.0100 / 5.2.5
VMware Tools for Windows 13.x / 12.x and 11.x 13.1.5.0 / 12.5.5

Two practical notes from Broadcom's Q&A: the update cannot be applied with vCenter Quick Patch, and moving to 8.0 U3m or 9.0.2.0200 currently blocks a direct upgrade to VCF 9.1.1 because of "back-in-time" upgrade restrictions. Broadcom suggests either upgrading vCenter straight to 9.1.1 or waiting for VCF 9.1.2 if that upgrade path matters to you. Check ESX interoperability before updating vCenter.

What to do now

  1. Patch vCenter first. Take a file-based backup and a snapshot, then update to the fixed build for your branch. Follow with SDDC Manager and VMware Tools for Windows.
  2. Restrict management access. vCenter's web, appliance management and SSH interfaces should be reachable only from dedicated admin hosts, not from general corporate networks and never from the internet.
  3. Look for signs of prior compromise. Based on the reported attack chain, review SSO for administrator accounts nobody created, check whether SSH on the appliance was enabled unexpectedly, and look for unusual logins to ESXi hosts. Use the indicators and YARA rules in Mandiant's report where available.
  4. Assume credential theft if exploitation is plausible. Patching does not undo stolen secrets. Rotate vCenter SSO credentials and the token signing certificate, and review Active Directory if domain controller disks were reachable from vCenter. Forged SAML tokens are a reminder that MFA protects the login step, not a stolen signing key; our guide to how passkeys and phishing-resistant authentication work explains where those boundaries are.
  5. Check remote-access appliances. If you run BeyondTrust Remote Support, confirm it is patched against CVE-2026-102764, since that was the reported entry point.

The other KEV additions

CISA's November 20 update also listed three other flaws, according to SecurityOnline's breakdown:

  • Cisco Expressway (CVE-2026-76466, CVSS 9.8): remote root command execution on clustered Expressway-C and Expressway-E nodes. Cisco's October 21 advisory lists X15.5.20 as the first fixed release and no workaround; at publication Cisco said it was not aware of malicious use, so the KEV listing indicates that has since changed.
  • Apache Roller (CVE-2026-129448): a pre-authentication deserialization flaw in the XML-RPC endpoint affecting 4.0.0 through 6.1.4. Third-party write-ups point to 6.1.6 as the first fixed release, with 6.1.7 current; confirm against the Apache Roller security page before relying on a specific version.
  • SAP NetWeaver Enterprise Portal (CVE-2025-42884): a JNDI injection issue addressed by an SAP security note.

KEV listings are a strong signal for prioritization even outside the US government. If you are building a patch queue, the same approach we described for the LiteLLM KEV addition applies here: exploited and internet-reachable first, then everything that can reach your management plane.

What is still unclear

  • Broadcom has not published how many customers were affected, and Mandiant has not said how many organizations it investigated beyond "multiple incidents."
  • Public reporting has not specified the full set of sectors or regions targeted.
  • Whether other actors now have working exploits is unknown; vCenter flaws have historically drawn rapid follow-on exploitation once details become public, so treat the patch window as short.

Frequently asked questions

+Is there a workaround for CVE-2026-123890?

No. Broadcom lists no workaround in VMSA-2026-0009. The only fix is updating vCenter to a patched build such as 8.0 U3m, 9.0.2.0200 or 9.1.1.0200.

+Can I apply the fix with vCenter Quick Patch?

No. Broadcom says this update is not eligible for vCenter Quick Patch, so plan a normal vCenter update and take a backup or snapshot first.

+Is ESXi affected by CVE-2026-123890?

Broadcom says ESX itself is not affected by VMSA-2026-0009. However, attackers who controlled vCenter in the reported intrusions went on to reach ESXi hosts, so compromised environments need a wider investigation.

+Does patching remove an attacker who is already inside?

No. The patch closes the vulnerability, but accounts, tokens or backdoors created before patching remain. If exploitation is plausible, investigate and rotate credentials and signing keys.

Sources & references

  1. Broadcom / VMware (GitHub) — VMSA-2026-0009 Questions & Answers (Nov 19, 2026)
  2. Help Net Security — VMware vCenter zero-day exploited for months before patch (Nov 20, 2026)
  3. CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog (Nov 20, 2026)
  4. SecurityOnline — CISA adds VMware vCenter, SAP NetWeaver, Cisco Expressway and Apache Roller flaws to KEV (Nov 21, 2026)
  5. Cisco — Cisco Expressway Series Remote Code Execution Vulnerability (cisco-sa-vcs-static-cred-hr7EWZ8t, Oct 21, 2026)

Spotted an error? See our Corrections Policy.

  • #vmware
  • #vcenter
  • #zero-day
  • #cve
  • #cisa-kev
  • #vsphere
  • #vulnerability
KB

KernelBrief Editorial

The KernelBrief editorial desk researches, writes and fact-checks every article published on this site. Every article is checked against primary sources (official documentation, vendor announcements, standards bodies and original research) before publication. Every factual claim is linked to its source, and corrections are handled under our published Corrections Policy.