Broadcom's November 19, 2026 fix for CVE-2026-123890 stops new attackers from using this flaw to get into vCenter. It does nothing about an attacker who got in earlier, and Google's Mandiant says one group was using the flaw in early September. The Cybersecurity and Infrastructure Security Agency (CISA) added it to the Known Exploited Vulnerabilities (KEV) catalog on Friday, November 20, with a due date of Monday, November 23, and flagged it for forensic triage.
What CVE-2026-123890 is
Broadcom's advisory, VMSA-2026-0009, describes an authentication bypass in the VMware Directory Service, rated 9.8 under CVSS 3.1: "A malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system." Broadcom credits Mandiant with the report and lists no workaround. The advisory itself doesn't describe exploitation; CISA's KEV listing and Google's analysis do.
Google's analysis, published the same day, says successful exploitation creates "an authenticated session established as [email protected]." It ties the September use to a group it tracks as ARMORY CASTLE, which reached vCenter from inside a network it had already entered through a BeyondTrust Remote Support appliance. That vCenter was already patched for July's CVE-2026-59309; Broadcom calls the new CVE "a new and distinct issue."
Broadcom says ESX is not affected and nothing in the advisory is a virtual machine escape. The flaw is present whether or not Enhanced Linked Mode is in use.
What the KEV entry asks agencies to do
The entry in CISA's JSON feed (catalog version 2026.11.20) reads: added 2026-11-20, due 2026-11-23, forensicTriage "Yes", ransomware use "Unknown." The required action points to Binding Operational Directive (BOD) 26-04 and CISA's forensic triage requirements, and says to "Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable."
CISA gave the same November 23 date to the three other entries it added that day: Cisco Expressway (CVE-2026-76466), Apache Roller (CVE-2026-129448) and SAP NetWeaver (CVE-2025-42884). Agencies must start remediating on BOD 26-04 timelines by December 7, 2026, and under the directive each system's timeline also turns on whether it is publicly exposed, as our KEV due dates explainer describes. Your CISO's office maps the directive's table to each vCenter.
The BeyondTrust Remote Support flaw Google names as the group's way in, CVE-2026-102764, has been in the KEV catalog since October 16, 2026, also flagged for triage. If your October triage of that appliance stopped at the appliance, extend it to the vCenter servers it could reach.
Which builds fix it
| Where vCenter runs | Fixed version (per VMSA-2026-0009) |
|---|---|
| vCenter 9.1.x (VCF and vSphere Foundation) | 9.1.1.0200 |
| vCenter 9.0.x (VCF and vSphere Foundation) | 9.0.2.0200 |
| vCenter 8.0 | 8.0 U3m |
| VMware Cloud Foundation 5.x | vCenter 8.0 U3m through async patching (KB 88287), SDDC Manager 5.2.5 |
| vCenter 7.0 | Through Broadcom Support with an extended support contract |
| Telco Cloud Platform and Telco Cloud Infrastructure | KB463116 |
| vSphere 6.5 and 6.7 | No patch listed; Broadcom says to presume affected |
Broadcom's FAQ adds the operational details. These updates can't go through vCenter Quick Patch, though the VAMI works. Workloads keep running during the update, but the vSphere Client drops out briefly and some encryption operations against a Standard Key Provider pause. And 8.0 U3m or 9.0.2.0200 blocks a later upgrade to VCF 9.1.1, a "Back-in-Time" conflict: Broadcom's options are to move vCenter to 9.1.1 first and patch there, or wait briefly for VCF 9.1.2.
What to check on vCenter and its hosts
A three-day window doesn't leave room to hold the patch for a full investigation. Export the vCenter and SSO logs and take an appliance snapshot or backup first, so the evidence survives, then install the fixed build and work through the checks.
Google describes what the group did once inside. Its exploit tool created a single sign-on (SSO) administrator account, copied the vmdir database (data.mdb) and extracted the private key the Security Token Service uses to sign SAML tokens; a second tool forged those tokens, which Google says can bypass multifactor authentication. The group then took vCenter's master crypto key and PostgreSQL credentials, signed in to an ESX host's Host Client as vpxuser and connected over SSH as root, added an SSH key to the host's root authorized_keys, and copied Active Directory database files out of guest virtual machine disks. ESX isn't vulnerable to this flaw, but it is within reach of whoever holds vCenter.
- On vCenter: account for every administrator and machine account in the vsphere.local SSO domain, paying attention to anything created since early September, and review logs for [email protected] sessions from unusual hosts and for SSH being switched on through the VAMI.
- On each ESX host it manages: check root's authorized_keys, SSH service history and logins by vpxuser or root, and look for unexpected hidden directories on VMFS volumes.
- Around it: check internal Linux appliances that can reach vCenter against Google's published file and network indicators, and treat domain controllers running as virtual machines as possibly exposed if the hosts were touched.
If anything turns up, the problem outlives the patch. Replacing the token signing certificate, resetting the SSO administrator and vpxuser credentials, rotating what vCenter stores and resetting domain credentials are steps to plan with your incident responders, under the agency's reporting rules. Our PHP2Shell walkthrough shows the same evidence-first order on an earlier KEV entry.
Limiting exposure while the change is scheduled
Broadcom says organizations "must decide for themselves" whether to rely on compensating controls such as firewalls. Google notes the exploit uses TCP port 2012, the control interface for vCenter SSO, and describes restricting management ports (443, 2012, 5480 and 22) to allowlisted administration hosts. It warns that the appliance's built-in VAMI firewall can't be scoped port by port and offers a hardening script, to be tested under change control first. They narrow who can reach the flaw without fixing it.
The other four CVEs, and who sets your date
VMSA-2026-0009 also fixes three flaws in SDDC Manager (CVE-2026-123891, CVE-2026-123892 and CVE-2026-123893, fixed in 9.1.1.0200, 9.0.2.0100 and 5.2.5) and a SAML token signature bypass in VMware Tools for Windows (CVE-2026-123894, fixed in 13.1.5.0 and 12.5.5) that applies where Guest Alias mapping is configured. None of the four was in the KEV catalog as of November 21, 2026; schedule them under the agency's BOD 26-04 timelines. The SDDC Manager flaws need an authenticated attacker, which makes them more pressing anywhere SSO credentials may have been taken.
BOD 26-04 binds federal civilian executive branch agencies. For a vCenter a contractor runs on an agency's behalf, the requirement usually reaches the contractor through the contract, and the contracting officer or agency security office says which date applies.
The Bottom Line
Treat every vCenter below the fixed build as possibly entered, not just unpatched. Preserve logs, install the fixed build, then check SSO accounts, host access and domain credentials, and plan certificate and credential changes with your incident responders if anything looks wrong. Our cybersecurity teams support federal programs on FISMA and NIST compliance.
FAQ
What is CVE-2026-123890?
It is an authentication bypass in the VMware Directory Service in vCenter, rated 9.8 under CVSS 3.1. Broadcom's advisory VMSA-2026-0009 says an attacker with network access to vCenter may bypass authentication and gain unauthorized access. Mandiant reported it to Broadcom.
Is VMware ESX affected by CVE-2026-123890?
No. Broadcom's advisory FAQ says ESX is not affected and none of the five flaws in VMSA-2026-0009 allows code to run on an ESX host from inside a virtual machine. An attacker with vCenter administrator access can still manage the hosts and virtual machines vCenter controls, which is why the fix matters.
Is there a workaround for the vCenter flaw?
Broadcom lists none. Its FAQ says firewalls and other compensating controls may reduce exposure but that each organization has to decide whether to rely on them. CISA's KEV entry says to follow BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable.
Does CVE-2026-123890 affect vSphere 7?
Yes. Broadcom's FAQ says vSphere 7 reached End of General Support on October 2, 2025, and customers with an active extended support contract should request patches through those support processes. It says to presume vSphere 6.5 and 6.7 are affected as well.
When is the KEV due date for CVE-2026-123890?
CISA added it to the Known Exploited Vulnerabilities catalog on November 20, 2026 with a due date of November 23, 2026, and flagged it for forensic triage. Agencies must be on BOD 26-04 timelines by December 7, 2026, and under that directive each system's timeline also depends on its exposure, so the agency security office maps it to each vCenter.
Sources
- Broadcom, VMSA-2026-0009, VMware vCenter, Tools, and SDDC Manager updates address multiple vulnerabilities (November 19, 2026; updated November 20, 2026)
- Broadcom, VMSA-2026-0009 Questions and Answers
- CISA, Known Exploited Vulnerabilities Catalog, JSON data feed (catalog version 2026.11.20)
- Google Threat Intelligence Group and Mandiant, ARMORY CASTLE Exploits vSphere (November 19, 2026)
- BleepingComputer, VMware patches vCenter zero-day exploited in attacks since September (November 19, 2026)
- The Hacker News, Critical VMware vCenter Zero-Day Flaw Lets Network Attackers Bypass Authentication (November 19, 2026)
How we researched this. Every number, date and requirement here is checked against the sources listed above, primary documents first, and the post is fact-checked again before publication. When a rule, date or status changes, we update the post and log the change below. Read our editorial standards or send a correction.





