# VMware vCenter CVE-2026-123890 (VMSA-2026-0009) detection pack

Pack 1.0.0, built 19 Nov 2026 (GMT). Folder `vmware-vcenter-cve-2026-123890-2026-11`. Proposed hubfs slot: `vmware-vcenter-cve-2026-123890-pack-v1`.

**Critical, because Broadcom scores it CVSS 3.1 9.8** (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-288). Patch now regardless of KEV status.

## What Broadcom says (VMSA-2026-0009, issue date 2026-11-19, initial advisory)

- Broadcom: "VMware vCenter contains an authentication bypass vulnerability in the VMware Directory Service."
- Known attack vectors, Broadcom: "A malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system." Broadcom does not say what level of access follows.
- Workarounds: None. Broadcom FAQ: "Not as listed by Broadcom." Compensating controls are the customer's own decision.
- Broadcom FAQ: "The vCenter issue qualifies under ITIL methodologies as an emergency change".
- Broadcom FAQ: "Patches are cumulative, so versions newer than the ones listed also resolve these issues."
- Broadcom FAQ: ESX is not affected by this VMSA. The issue is present whether or not Enhanced Linked Mode is used. None of the issues is a VM escape.
- Broadcom FAQ: "The vCenter updates in this advisory are not eligible for vCenter Quick Patch."
- Broadcom FAQ: CVE-2026-123890 is "a new and distinct issue" from CVE-2026-59309 (VMSA-2026-0006).
- The issues were privately reported to Broadcom. Research is credited to security researchers only.

## Affected and fixed (Broadcom response matrix and release notes)

| Product line | Affected | Fixed version | Fixed build (Broadcom release notes) |
|---|---|---|---|
| VCF and VVF vCenter 9.1.x | 9.1.x below 9.1.1.0200 | 9.1.1.0200 | 25901347 |
| VCF and VVF vCenter 9.0.x | 9.0.x below 9.0.2.0200 | 9.0.2.0200 | 25901331 |
| vCenter 8.0 | 8.0 below 8.0 U3m | 8.0 U3m (appliance version 8.0.3.01200) | 25934264 |
| VCF 5.x | 5.x below 5.2.5 | 5.2.5: apply vCenter 8.0 U3m by async patching (KB 88287) and update SDDC Manager to 5.2.5 | 25934264 (vCenter 8.0 U3m) |
| vCenter 7.0 | listed by Broadcom as affected | contact Broadcom Support under an extended support contract | none published |
| Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 and Telco Cloud Infrastructure 3.0 | affected (KB 463116) | vCenter 8.0 U3m (KB 463116) | 25934264 |

- vSphere 7.0: Broadcom lists it in the response matrix. Broadcom FAQ: "VMware vSphere 7 reached End of General Support on October 2, 2025." Patches come through extended support only.
- vSphere 6.5 and 6.7: not listed. Broadcom FAQ: "Presume that it does." Broadcom does not evaluate products past End of General Support. The checker reports these as EOS PRESUMED AFFECTED.
- Upgrade path, Broadcom FAQ: "vCenter 8.0 U3m and 9.0.2.0200 block upgrades to VCF 9.1.1, and customers should wait, briefly, for VCF 9.1.2." This is a "Back-in-Time" restriction: 8.0 U3m (build 25934264) carries a higher build than 9.1.1.0200 (build 25901347). If a VCF 9.1 upgrade is planned, upgrade vCenter to 9.1.1 first and apply 9.1.1.0200 there, or wait for VCF 9.1.2.
- Each fixed release note states: "This release resolves CVE-2026-123890."

## Other CVEs in the same advisory (Broadcom severities)

| CVE | Product | Broadcom severity | CVSS 3.1 | Fixed |
|---|---|---|---|---|
| CVE-2026-123891 | SDDC Manager, SQL injection (authenticated) | Important | 8.1 | 9.1.1.0200 (9.1.x), 9.0.2.0100 (9.0.x), 5.2.5 (5.x) |
| CVE-2026-123892 | SDDC Manager, authenticated command injection | Important | 7.2 | as above |
| CVE-2026-123893 | SDDC Manager, local privilege escalation to root | Moderate | 6.7 | as above |
| CVE-2026-123894 | VMware Tools for Windows, SAML token signature bypass (local privileged process in the guest) | Moderate | 6.7 | Tools 13.1.5.0 (13.x), 12.5.5 (12.x and 11.x), 12.4.10 for 32-bit |

The advisory as a whole has CVSSv3 range 6.7 to 9.8.

## Exploitation and KEV

- no exploitation reported by Broadcom or CISA as of 19 Nov 2026. Not in CISA KEV (catalogue 2026.11.18, released 18 Nov 2026 19:17 GMT).
- NEWS, reported via The Hacker News (19 Nov 2026): Broadcom has not reported attacks or public exploit code. This is THN's framing of Broadcom's position; Broadcom's advisory and FAQ do not address exploitation.
- KEV due dates apply to US federal agencies only (BOD 26-04). Patch now regardless of KEV status.
- July context, CISA KEV wording: CVE-2026-59310 "Broadcom VMware vCenter Path Traversal Vulnerability", added 18 Aug 2026, Known Ransomware Campaign Use: Known. NVD describes it as a directory traversal in the vCenter Syslog server, not vmdir. CVE-2026-59309 (the July vmdir authentication bypass, CVSS 9.8) is not in KEV.
- Timeline: CVE record published 19 Nov 2026 14:02 GMT (CNA VMware); NVD published 15:17 GMT, status Received.

## Corrections for Webite builder (TVF flag of 19 Nov 2026 15:29 GMT)

1. VMSA ID confirmed: VMSA-2026-0009 (Broadcom notification 39495), issue date 2026-11-19.
2. vSphere 7.0 is listed by Broadcom as affected (patch via extended support), not only presumed. 6.5 and 6.7 are presumed affected in Broadcom's own FAQ, not only per THN.
3. Fixed builds: 9.1.1.0200 build 25901347; 9.0.2.0200 build 25901331; 8.0 U3m (8.0.3.01200) build 25934264. VCF 5.x: vCenter 8.0 U3m via async patching (KB 88287) plus SDDC Manager 5.2.5. Telco Cloud: vCenter 8.0 U3m (KB 463116).
4. Quick Patch and the VCF 9.1.1 upgrade block come from Broadcom's FAQ, not only THN.
5. Other CVEs: CVE-2026-123891 Important 8.1, CVE-2026-123892 Important 7.2, CVE-2026-123893 Moderate 6.7, CVE-2026-123894 Moderate 6.7. SDDC Manager 9.0.x fix is 9.0.2.0100.
6. July: only CVE-2026-59310 (path traversal in the Syslog server) is in KEV, with known ransomware campaign use. CVE-2026-59309 is not in KEV. Do not describe the July vmdir bugs as attacked in the wild or tie ESXi ransomware to CVE-2026-59309.
7. Exploitation: Broadcom's advisory and FAQ do not address exploitation; not in KEV.
8. Credit security researchers only.

## Checker (read only, offline)

`scripts/check-vcenter-123890.sh` (bash) and `scripts/Check-Vcenter123890.ps1` (PowerShell 7) give identical output and exit codes. They open no network connection, write no file, run no program and print only versions, builds, row numbers and cleaned names, never other columns.

```
bash scripts/check-vcenter-123890.sh --version-string 8.0.3.01200 --build 25934264
bash scripts/check-vcenter-123890.sh --version-string "8.0 U3m"
bash scripts/check-vcenter-123890.sh --build 25901347
bash scripts/check-vcenter-123890.sh --file vcenters.csv
pwsh -File scripts/Check-Vcenter123890.ps1 -File vcenters.txt
```

Inputs: a version string (appliance version such as 8.0.3.01200, 9.0.2.0200, 9.1.1.0200, an update name such as 8.0 U3m, or the PowerCLI Version such as 8.0.3), a build, or a saved file. Broadcom FAQ: after `Connect-VIServer`, the build is in `$global:DefaultVIServer.Build` and the version in `$global:DefaultVIServer.Version`; the vSphere Client Summary tab also shows the build. Files can be PowerCLI Format-List output (`Name`, `Version`, `Build` lines; one block per vCenter) or a CSV with `Version` and/or `Build` columns and optional `Name` (Export-Csv `#TYPE` lines are skipped). Export only what is needed, for example `$global:DefaultVIServer | Select-Object Name, Version, Build | Export-Csv vcenters.csv -NoTypeInformation`.

| Exit | Meaning |
|---|---|
| 0 | FIXED |
| 1 | not used (reserved for unexpected runtime errors) |
| 2 | AFFECTED (any target) |
| 3 | REVIEW OR UNKNOWN |
| 4 | not used |
| 5 | USAGE OR READ ERROR |
| 6 | EOS PRESUMED AFFECTED |

Several targets: any AFFECTED gives 2, else any EOS PRESUMED AFFECTED gives 6, else any REVIEW gives 3, else 0. Limits: 4 MiB file, 64 KiB line, 2000 targets.

OUR ASSUMPTION: within one release branch, a higher build or appliance patch number is a later release. Only the three fixed builds above are taken from Broadcom; a version like 8.0.3 or 9.0.2 with no build is REVIEW. A documented fixed version with a different build is REVIEW. Versions after the fixed ones in the same branch are FIXED because Broadcom says patches are cumulative. 9.2 and later are REVIEW. When the verdict is for the 8.0 or 9.0 branch the checker prints the VCF 9.1.1 upgrade note.

## Manual reachability checks (OUR ADVICE (CybaVerse, not from Broadcom))

Run from a host outside the management network (for example a user VLAN, and from the internet), replacing `vcenter.example.com`:

```
nc -vz -w 3 vcenter.example.com 443
nc -vz -w 3 vcenter.example.com 389
nc -vz -w 3 vcenter.example.com 636
Test-NetConnection -ComputerName vcenter.example.com -Port 389
```

A successful connection from outside management ranges means vCenter is exposed to more of the network than it should be. These checks are not in the checker, which stays offline. Ports: Broadcom KB 301632 shows LDAP 389 and LDAPS 636 to vCenter Single Sign-On (vmdird); KB 461567 lists TCP 636 for vmdird (LDAPS between vCenter Servers in Enhanced Linked Mode); KB 313841 lists rhttpproxy 443 and vmdird 636. Restricting these ports reduces exposure; it is not a Broadcom workaround and not a fix.

## Hunts (kql/vmware-vcenter-cve-2026-123890-hunting.kql)

The KQL in this pack has NOT been run against a live tenant. It was parsed with Kusto.Language against Microsoft Learn schemas. Fill `VCenterServers`, `MgmtRanges`, `MgmtDevices`, `VCenterHostNames` and `EsxHostNames` first.

| Hunt | Table | What it finds |
|---|---|---|
| Q1 OUR PATTERN | CommonSecurityLog | vCenter 443, 389 or 636 reached from outside management ranges and other vCenters |
| Q2 OUR PATTERN | DeviceNetworkEvents | Endpoints (Windows and others in Defender) connecting to vCenter LDAP 389 or 636 |
| Q3 OUR PATTERN | CommonSecurityLog | New sources of vmdir LDAP traffic against a 30 day baseline |
| Q4 OUR PATTERN | Syslog | vCenter SSO account and privilege changes [UNVERIFIED] term |
| Q5 OUR PATTERN | Syslog | ESX service access enabled, including SSH (Broadcom KB 423683 text) |
| Q6 OUR PATTERN | Syslog | Many VM power-offs on one ESX host [UNVERIFIED] term |
| Q7 OUR PATTERN | Syslog | Many snapshot removals on one ESX host [UNVERIFIED] term |
| Q8 OUR PATTERN | Syslog | vCenter or ESX hosts that stopped sending syslog |

Log sources (Broadcom): SSO writes audit events (Login and Logout, Privilege Change, Account Change, Security Change, Account Enabled or Disabled, Identity Source) to `audit_events.log` in `/var/log/audit/sso-events/` (Single Sign-On Audit Events). ESX: `hostd.log` is the host agent log and holds VM and host tasks and events; `shell.log` records ESX Shell commands and shell events such as enabling the shell; `auth.log`, `syslog.log`, `vpxa.log` and `vmkernel.log` are also listed (ESX Log File Locations, KB 306962). KB 423683 shows hostd lines `eventTypeId = "esx.audit.<services_name>.enabled"` and `<services_name> access has been enabled.` with `esx.audit.ssh.enabled` for SSH.

[UNVERIFIED] Broadcom does not document the forwarded syslog text for SSO audit events, VM power-off or snapshot removal. Q4 uses `com.vmware.sso.PrincipalManagement`, named in the DISA vCenter 8.0 STIG, not by Broadcom. Q6 and Q7 use vSphere API names (`VmPoweredOffEvent`, `RemoveSnapshot_Task`) that may not appear as log text. Check your own forwarded lines and adjust before relying on them. Broadcom does not document a vCenter appliance SSH enablement log line, so there is no KQL for it; check the appliance settings by hand.

## Sigma (sigma/)

| Rule | Logsource | Level |
|---|---|---|
| vcenter_vmdir_ldap_from_non_management.yml | firewall | high |
| vcenter_https_from_non_management.yml | firewall | medium |
| vcenter_vmdir_ldap_from_windows_endpoint.yml | windows network_connection | medium |
| esx_service_access_enabled.yml | custom vmware esx | medium |

All rules are OUR PATTERN and use RFC 5737 placeholders (192.0.2.0/24 for vCenter, 198.51.100.0/24 for management). Conversions to Kusto for five pipelines (no pipeline, microsoft_xdr, microsoft_365_defender, sentinel_asim, azure_monitor) are in `sigma/converted/`; the conversions have 12 documented failures (firewall and custom logsources have no table in the Microsoft pipelines). The microsoft_xdr and microsoft_365_defender output for the Windows rule drops `Initiated`; filter outbound connections yourself.

## Response

Vendor (Broadcom): apply the fixed version for each branch above; there is no workaround; treat it as an emergency change.

OUR ADVICE (CybaVerse, not from Broadcom):
- Patch every vCenter now, internet-facing and MSP-managed client vCenters first. Run the checker on a PowerCLI export of every vCenter.
- Limit 443, 389 and 636 on vCenter to management networks and jump hosts; this reduces exposure only.
- Replace or isolate 6.5, 6.7 and unsupported 7.0 vCenters.
- Keep vCenter and ESX backups offline and immutable.
- If compromise is suspected: isolate vCenter, rotate SSO, administrator@vsphere.local and service account credentials, review SSO users and groups, rebuild from known-good media and engage incident response.

## MITRE ATT&CK

- T1190 Exploit Public-Facing Application (Q1 to Q3, network Sigma rules)
- T1098 Account Manipulation and T1136 Create Account (Q4)
- T1021.004 Remote Services: SSH (Q5, esx_service_access_enabled.yml)
- T1529 System Shutdown/Reboot (Q6)
- T1490 Inhibit System Recovery (Q7)

## Sources (fetched 19 Nov 2026)

- Broadcom VMSA-2026-0009: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495
- Broadcom FAQ "VMSA-2026-0009: Questions & Answers" (linked from the advisory)
- vCenter 8.0 U3m release notes: https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u3m-release-notes.html
- vCenter 9.1.1.0200 release notes: https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/release-notes/patch-releases-9-1-1-x/vsphere/vcenter/vcenter-9-1-1-0200-release-notes.html
- vCenter 9.0.2.0200 release notes: https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/release-notes/patch-releases-9-0-0-x/vsphere/vcenter/vcenter-9-0-2-0200-release-notes.html
- KB 463116 (Telco Cloud): https://knowledge.broadcom.com/external/article/463116
- KB 88287 (VCF async patching): https://knowledge.broadcom.com/external/article?legacyId=88287
- KB 301632: https://knowledge.broadcom.com/external/article/301632/using-jxplorer-to-connect-to-the-vsphere.html
- KB 461567: https://knowledge.broadcom.com/external/article/461567/ports-636-and-3128-continue-to-present-t.html
- KB 313841: https://knowledge.broadcom.com/external/article/313841
- KB 423683: https://knowledge.broadcom.com/external/article/423683/how-to-confirm-and-compare-esxi-service.html
- KB 306962: https://knowledge.broadcom.com/external/article/306962/location-of-esxi-log-files
- ESX Log File Locations (vSphere 9.1): https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/9-1/vsphere-security/securing-esxi-hosts/managing-esxi-log-files/esxi-log-file-locations.html
- Single Sign-On Audit Events (vSphere 8.0): https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security/understanding-vsphere-hardening-and-compliance/audit-logging/single-sign-on-audit-events.html
- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123890
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123890
- NVD CVE-2026-59310: https://nvd.nist.gov/vuln/detail/CVE-2026-59310
- CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- The Hacker News: https://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.html
- MITRE ATT&CK: https://attack.mitre.org/techniques/T1190/
- Microsoft Learn table schemas: https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/commonsecuritylog

## Tests

`bash tests/run_all.sh` runs shellcheck, PSScriptAnalyzer, the bash tests, the Pester tests (bash and PowerShell compared byte for byte), the static gates, the KQL parse check (and a check that it rejects an unknown column), sandboxed checker runs with no network and a read-only filesystem, Sigma check and conversion comparison, then `tests/negative_gates.sh`, which plants faults in a temporary copy and confirms the gates catch each one.

## Files

README.md; kql/; scripts/; sigma/ and sigma/converted/; tests/ (fixtures are synthetic and marked FIXTURE_ONLY).
