For: IT and platform teams running vCenter Server, VMware Cloud Foundation (VCF) or Telco Cloud products. This article is based on Broadcom's advisory, CVE.org and the CISA KEV data; it does not cover attack steps.
続報待ち:この記事は公式発表に合わせて更新します
- Who is affected
IT and platform teams running vCenter Server, VMware Cloud Foundation (VCF) or Telco Cloud products.
- Confirmed so farSee the table ↓
- The flaw
- Affected and fixed versions
- Workaround
2 more
- Exploitation
- CISA KEV
- Not yet confirmed
- Whether further victims or other attack routes are reported (the report describes one campaign only)
- Whether Broadcom updates its advisory to mention exploitation (not mentioned as of November 21)
- A fix for vCenter 7.0 (Broadcom says extended-support customers should contact it)
- What to do nowSee the steps ↓
- Check your vCenter version
- Update to a fixed release
- Things to watch around the update
2 more
- Check the other fixes in the same advisory
- Look for signs of compromise
- Where to verify (source)All sources ↓
- Broadcom
- Last checked
- as of November 21, 2026
Follow-up plans and what we checked
Broadcom's advisory and the CVE record were published on November 19. Broadcom's advisory does not mention exploitation. On November 20, a major cloud provider's threat-intelligence team published a report saying a suspected state-linked espionage group exploited the flaw as a zero-day from early September 2026, based on forensic evidence, and then reached vCenter and ESXi hosts. The same day CISA added the CVE to KEV with a federal due date of November 23, and its SSVC entry now says Exploitation: active. Attribution of the activity is the reporting company's assessment and we do not state it as fact. Our earlier update recorded the exploitation as press coverage only; the report itself is now the source.
What to do today
Check your vCenter version
The Summary tab in the vSphere Client shows the vCenter version and build (Broadcom guidance). Affected: 9.1.x, 9.0.x, 8.0 and VCF 5.x. Broadcom says to assume unlisted older versions (such as 6.5 and 6.7) are affected. vSphere 7 reached end of general support on October 2, 2025; with an extended support contract, request patches through that process.
Update to a fixed release
Per Broadcom's advisory, the fixes are 9.1.1.0200 for vCenter 9.1.x, 9.0.2.0200 for 9.0.x, 8.0 U3m for 8.0, and 5.2.5 for VCF vCenter 5.x. Telco Cloud Platform (3.0, 4.x, 5.0.x, 5.1.x, 5.2) and Telco Cloud Infrastructure 3.0 follow KB463116. These updates are not eligible for vCenter Quick Patch. During the update the vSphere Client and other management tools are unavailable, but running VMs keep running (Broadcom guidance). Check the Interoperability Matrix for ESX compatibility first.
Things to watch around the update
8.0 U3m and 9.0.2.0200 include a Back-in-Time restriction that blocks upgrading to VCF 9.1.1. If you are mid-upgrade, read Broadcom's FAQ and interoperability matrix first. While waiting to update, limit sources that can reach the vCenter management interfaces to a management network and VPN (a general defensive measure, not a Broadcom workaround; judge its effect for yourself).
Check the other fixes in the same advisory
VMSA-2026-0009 also covers SDDC Manager (CVE-2026-123891 to 123893) and VMware Tools for Windows (CVE-2026-123894). SDDC Manager fixes are 9.1.1.0200, 9.0.2.0100 and 5.2.5; VMware Tools is 13.1.5.0 or 12.5.5. Confirm your products in the advisory's tables.
Look for signs of compromise
Because exploitation is confirmed, check vCenter and upstream logs for the period before the fixes were available for unexpected administrator logins or unfamiliar operations. No match does not prove you are clean. If anything looks wrong, isolate vCenter and rotate the administrator credentials and any credentials vCenter stores (how to check for intrusion).
What kind of flaw this is
- CVE
- CVE-2026-123890 (VMware vCenter: authentication bypass in the VMware Directory Service)
- Severity
- CVSS v3.1 9.8 (CRITICAL; AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
- Type
- Authentication bypass using an alternate path or channel (CWE-288)
- Impact
- An attacker with network access may bypass authentication and access the system as Administrator (Broadcom)
- Affected
- vCenter 9.1.x, 9.0.x, 8.0, VCF vCenter 5.x, Telco Cloud Platform and Infrastructure (7.0 for extended-support customers)
- Fix
- 9.1.1.0200, 9.0.2.0200, 8.0 U3m, 5.2.5 (Broadcom). No workaround
- Published
- November 19, 2026 (Broadcom advisory VMSA-2026-0009; CVE record)
- Exploitation
- Not mentioned in Broadcom's advisory. Reported by a major cloud provider's threat-intelligence team (zero-day since early September). In CISA KEV since November 20, due November 23
- In short: the authentication handling in the VMware Directory Service has a flaw that lets it be bypassed (Broadcom). The advisory gives no further mechanism, and we do not include request details.
- The flaw was reported to Broadcom by a security company (credit in the advisory).
- The advisory does not mention exploitation. the threat-intelligence team's report of November 20 says activity began in early September, before fixes existed, and that the intruders went on to vCenter and ESXi hosts.
- CISA's KEV entry carries a forensic triage flag and a federal due date of November 23. Treat the update as an emergency change even if you are not a US federal agency.
- Some reports describe the intrusions as chaining other flaws; this page does not cover that.
What is known and what is not
| Item | Content | Status |
|---|---|---|
| The flaw | Authentication bypass in the VMware Directory Service | Confirmed (Broadcom, CVE.org) |
| Affected and fixed versions | 9.1.1.0200, 9.0.2.0200, 8.0 U3m, 5.2.5; 7.0 for extended-support customers | Confirmed (Broadcom) |
| Workaround | None | Confirmed (Broadcom) |
| Exploitation | Zero-day exploitation from early September; not in Broadcom's advisory | Confirmed (a major cloud provider's threat-intelligence team report; CISA KEV) |
| CISA KEV | Added November 20, due November 23 | Confirmed (KEV data) |
| Attribution | The report names a suspected state-linked group; attribution is the reporting company's view | We do not state it as fact |
Sources
- Broadcom — VMSA-2026-0009 (November 19; affected versions, fixed versions, no workaround, credit)
- Broadcom — VMSA-2026-0009 FAQ (cumulative patches, vCenter 7.0, how to find your version)
- CVE.org — CVE-2026-123890 (published November 19, 2026)
- CISA KEV — Known Exploited Vulnerabilities Catalog (added November 20, due November 23)
- Threat-intelligence report — a major cloud provider's threat-intelligence team's report on the exploitation (November 20; the reporting company's own material)
- SecurityWeek — Press coverage of the same report (press coverage of the same report)
- Security firm — A security firm's explainer (a security firm's explainer; cross-checked with primary sources)
Attack steps and indicators of compromise (IOCs) are not included. Last verified: November 21, 2026.
Update history
2026-11-21: Updated. CISA added the CVE to KEV on November 20 (due November 23), and a major cloud provider's threat-intelligence team's own report confirms zero-day exploitation from early September. Exploitation is no longer recorded as press coverage only.
2026-11-20: First report. Based on Broadcom's advisory, CVE.org and the CISA KEV data; exploitation is recorded separately as press coverage.
Read next
- Related: VMware ESX logging flaw CVE-2026-41709 (listed in KEV)
- Practice: Vulnerability remediation playbook / Asset inventory checklist
- Prioritizing: Deciding fix order with CVSS, EPSS and KEV
- Checking: How to check for intrusion
- Term: What RCE (remote code execution) is