On this page (6 sections)
Broadcom has released fixes for CVE-2026-123890, a critical authentication bypass in the VMware Directory Service of vCenter Server. According to Rapid7's summary, Mandiant and Google Threat Intelligence confirmed in-the-wild exploitation by a suspected Chinese state-linked group tracked as ARMORY CASTLE (formerly UNC5221) as early as September 2026, well before the patches arrived on November 19, 2026. The flaw has also been added to the CISA Known Exploited Vulnerabilities (KEV) catalog.
If you run vCenter, especially on a network reachable from other internal systems, this is an emergency update. It applies even if you already installed the earlier July 2026 vCenter fix, because that was a different vulnerability.
What happened
According to Rapid7's summary of Broadcom advisory VMSA-2026-0009, a remote attacker with network access to vCenter can bypass authentication without credentials and gain access as the Administrator user. Mandiant privately reported the flaw to Broadcom.
The Hacker News reports that Google and Mandiant tied the exploitation to a wider intrusion campaign that also abused a then zero-day in BeyondTrust Remote Support (CVE-2026-102764). In that account, the group used the BeyondTrust foothold to move to an internal Linux appliance, scan for VMware-related ports, and then reach vCenter.
Help Net Security notes that the Broadcom advisory itself makes no mention of the in-the-wild exploitation found by Google's researchers, so the vendor bulletin alone will not tell you this is already being abused. Mandiant CTO Charles Carmakal advised organizations to both apply the patches and examine their systems for evidence of compromise. Note that The Hacker News and Help Net Security are both relaying the same Google and Mandiant findings, so they are not independent confirmations of each other.
CISA KEV listing
The vulnerability data for this CVE shows it was added to the CISA Known Exploited Vulnerabilities catalog on November 20, 2026, with a due date of November 23, 2026. The required action is to apply mitigations in accordance with vendor instructions, or to discontinue use of the product if mitigations are unavailable (the full wording is truncated in the data we have). Known ransomware campaign use is listed as Unknown. The NVD record is at NVD CVE-2026-123890. KEV due dates formally bind US federal agencies, but any organization can treat a KEV listing as a prompt to prioritize.
Technical details
The weakness is classed as CWE-288, authentication bypass using an alternate path or channel: the product requires authentication, but another route skips it (GitHub advisory). The CVSS vector is AV:N/AC:L/PR:N/UI:N, meaning it is network-reachable, low complexity, and needs no privileges or user interaction.
Google and Mandiant, quoted by The Hacker News, describe it as an unauthenticated Secure Remote Password (SRP-6a) session key disclosure over DCE/RPC. Successful exploitation yields an authenticated session as administrator@vsphere.local. They say the attacker's tooling was used to copy the directory database (LMDB), take over the SAML Security Token Service, and create a Single Sign On administrator account.
The same reporting says forged SAML tokens ('Golden SAML') could then let the attacker bypass multi-factor authentication and impersonate users. That matters for response: patching closes the entry point but does not remove access an attacker already created. Help Net Security notes the directory database holds the key used to sign login tokens, which is why a copied database is a lasting risk.
Who is affected
Any vCenter Server deployment below the fixed builds is affected, including vCenter inside VMware Cloud Foundation, vSphere Foundation, Telco Cloud Platform and Telco Cloud Infrastructure. Rapid7 relays Broadcom's FAQ statement that all systems below the fixed versions need this update, including those that already received the earlier fix for CVE-2026-59309.
| Product | Affected line | Fixed version / action |
|---|---|---|
| Cloud Foundation / vSphere Foundation | 9.1.x.x | 9.1.1.0200 |
| Cloud Foundation / vSphere Foundation | 9.0.x.x | 9.0.2.0200 |
| vCenter Server | 8.0 | 8.0 U3m |
| vCenter Server | 7.0 | Contact Broadcom Support (extended support customers) |
| Cloud Foundation | 5.x | 5.2.5 |
| Telco Cloud Platform | 3.0, 4.x, 5.0.x, 5.1.x, 5.2 | 8.0 U3m (KB463116) |
| Telco Cloud Infrastructure | 3.0 | 8.0 U3m (KB463116) |
The earlier CVE-2026-59309 has its own fixed versions in Broadcom's VMSA-2026-0006. Do not use that table for this issue, since the builds differ.
What to do now
- Inventory every vCenter Server and note its exact version and build.
- Compare each against the fixed versions in the table above and plan an emergency update outside the normal patch cycle. With exploitation confirmed and a KEV listing, do not wait for the next maintenance window.
- Back up vCenter, then apply the update with the standard update mechanism for your deployment, not Quick Patch.
- If you are mid-upgrade to VMware Cloud Foundation 9.1.1, read Broadcom's FAQ first: 8.0 U3m and 9.0.2.0200 add a 'Back-in-Time' restriction that blocks upgrades to 9.1.1.
- vCenter 7.0 owners without extended support have no listed fix, so isolate those systems and contact Broadcom Support.
- Restrict network access to vCenter management and SSO interfaces to a small set of admin hosts. This reduces exposure but is not a substitute for patching, since Broadcom lists no workaround.
- After patching, review for signs of prior compromise (see below) rather than assuming a clean system.
Detection and monitoring
Because exploitation began in September, check back at least that far. Based on the reported activity, look for:
- Unexpected local or SSO administrator accounts on vCenter, or new accounts created around the time of any suspicious access.
- Logins as administrator@vsphere.local from unusual source addresses.
- Internal port scans touching ports 9080, 5480 and 2012. Google notes port 2012 is the control interface RPC for vCenter SSO.
- Unknown SSH listeners or outbound traffic from Linux appliances near vCenter, such as a listener on TCP port 33992 reported in this campaign.
- Unexpected access to the directory database or changes to SAML/STS configuration.
- Compromised or unmonitored internal Linux appliances and edge devices, which were the stepping stones in the reported intrusion and, per Help Net Security, had no EDR tooling.
Google's report, as summarized by Help Net Security, includes indicators of compromise and YARA rules for threat hunting, and recommends going beyond patching: the vCenter appliance's built-in firewall can be switched off by anyone who reaches its management interface, which the attackers did. Google points to Mandiant's VCSA Hardening & Logging Tool, which blocks network access by default, filters outbound traffic and forwards logs to a SIEM.
If you find evidence of compromise, treat it as a full incident and involve your incident response team. As general practice, that usually means rotating credentials and reviewing SSO and signing material, but the reporting does not state what rotation steps Broadcom recommends, so check the vendor FAQ. The guide website hacked: what to do covers general recovery thinking, though it is written for websites rather than virtualization infrastructure.
Edge devices were the way in here, so keep an eye on what your own perimeter exposes. Webforta Monitor can watch certificate, DNS and header changes on public hosts, and the free SSL checker is a quick way to review a public endpoint. Neither inspects vCenter itself.
Timeline
| Date | Event |
|---|---|
| July 13, 2026 | Build timestamp in a recovered BONESAW binary (can be modified, per the reporting) |
| July 29, 2026 | Broadcom publishes VMSA-2026-0006 covering CVE-2026-59309 |
| September 2026 | Earliest confirmed exploitation of CVE-2026-123890 (Mandiant/Google) |
| November 19, 2026 | Broadcom publishes VMSA-2026-0009 and fixes for CVE-2026-123890 |
| November 20, 2026 | CVE-2026-123890 added to the CISA KEV catalog, with a due date of November 23, 2026 |
Story updates
CISA added CVE-2026-123890 to its Known Exploited Vulnerabilities catalog on November 20, 2026 (due date November 23, ransomware use unknown). We also added Help Net Security's details on the advisory omitting exploitation, Mandiant's evidence of pre-July knowledge, and Google's hardening and threat-hunting guidance.
First published.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
- CVE-2026-123890 - GitHub Advisory Database
- Support Content Notification - Support Portal - Broadcom support portal
- VMWare vCenter Authentication Bypass Using an Alternate Path or Channel Vulnerability (CVE-2026-123890) is being actively exploited
- VMware vCenter zero-day exploited for months before patch (CVE-2026-123890) - Help Net Security
- China-Linked Hackers Exploit Critical VMware vCenter Zero-Day to Gain Admin Access and Steal Data
- CVE-2026-123890: Critical Authentication Bypass in VMware vCenter
