CVE-2026-41709: Broadcom VMware ESX, is it exploitable where you run it
Code called: yesReached: yesControl in front: noExploitation known: yesWalk it through the four questions
What the flaw is
VMware ESX does not write a log entry for some administrative operations (CWE-778, insufficient logging). Broadcom says a malicious administrator could use this to perform certain operations without them being logged. The advisory does not name the operations.
The flaw gives an attacker no new access. It needs ESX administrator rights already, and it changes no data or service by itself. What the attacker gains is a quieter trail: actions taken with those rights are missing from the host's logs, so an incident responder who relies on ESX logs may miss them. Broadcom rates it 2.7 (CVSS base score), Low (integrity impact low, nothing else). It is one of five CVEs fixed in advisory VMSA-2026-0006, which Broadcom rates Critical overall. The advisory's Critical CVEs are two 9.8 vCenter flaws (CVE-2026-59309, an authentication bypass, and CVE-2026-59310, a directory traversal) and a 9.3 ESX VMXNET3 out-of-bounds write (CVE-2026-47876). CVE-2026-41703 is rated Important (7.6).
Broadcom credits Ian Barton of CrowdStrike with the report.
Are you exposed: each condition and how to check it
| Condition for exposure | How to check it on your system |
|---|---|
| the host runs ESX 9.0, 8.0, VMware Cloud Foundation 5.x or Telco Cloud Platform 5.x below its fixed build (ESX 9.1 is not affected) | On the host (SSH or ESXi Shell) run esxcli system version get and read the Build field, or run vmware -vl. In the Host Client the same build shows under Help > About. Compare with 25595025 (9.0) or 25429389 (8.0). A 9.1 host is not affected: Broadcom lists the 9.1.0.0 release, build 25370933, as the fixed version, so every 9.1 build has the fix. To see the installed image profile name, run esxcli software profile get. For VMware Cloud Foundation 5.x or Telco Cloud Platform, read the product version in SDDC Manager or the Telco Cloud Platform documentation, then confirm the build on each host with esxcli system version get: 25429389 or higher in the 8.0 U3 train (the versions table explains why), which is also the Telco Cloud Platform fix, ESXi80U3j-25429389. |
| an attacker holds administrator rights and can reach the management interface | List who holds them: esxcli system permission list on the host, and in vCenter the host's Permissions tab. Review local accounts and any Active Directory group mapped to the Administrator role, and the vSphere SSO groups that reach the host. Check lockdown mode with vim-cmd -U dcui vimsvc/auth/lockdown_is_enabled, and review the host firewall with esxcli network firewall ruleset list for services such as sshServer and vSphere Web Access, and the allowed IP list on each. |
Affected and fixed versions
Scroll the table sideways for more columns
| Product line | Component and version | Fixed version | Workaround |
|---|---|---|---|
| VMware Cloud Foundation, VMware vSphere Foundation | ESX 9.1.x.x | ESXi-9.1.0.0-25370933, the 9.1.0.0 release itself; no 9.1 build is affected | None |
| VMware Cloud Foundation, VMware vSphere Foundation | ESX 9.0.x.x | ESXi-9.0.2.0100-25595025 | None |
| VMware ESX | 8.0 | ESXi80U3j-25429389 | None |
| VMware Cloud Foundation | ESX 5.x | VMware Cloud Foundation 5.2.4, a VCF release; the matrix names the release, not an ESX build | None |
| VMware Telco Cloud Platform | ESX 5.0.x and 5.1.x | ESXi80U3j-25429389 (8.0 U3j), per KB449886 | None |
If the fix cannot go in yet
- Broadcom lists no workaround. Apply the fixed build for your line from the versions table. Cost: the host must enter maintenance mode and reboot, so plan vMotion or a rolling cluster update.
- Until the patch is in, cut the number of people and systems that hold ESX administrator rights and restrict who can reach the host management interface. This is general hardening, not a Broadcom instruction. Cost: administrators lose direct host access and must go through vCenter or a jump host. It does not remove the flaw: an administrator you still allow can use it.
- Forward ESX syslog to a remote collector (esxcli system syslog config set --loghost=
, then esxcli system syslog reload). This is general hardening, not a Broadcom instruction. It protects the entries that are written from later deletion on the host, but it cannot capture the operations this flaw leaves unlogged. It does not decide exposure, so it is not a condition above.
What to look for
- Broadcom does not name which operations go unlogged, and no vendor or CISA source publishes a log string, event ID or file path for this CVE, so the host logs hold nothing to search for.
- Compensating check for unlogged administrator actions: compare the host's own record (/var/log/hostd.log, /var/log/auth.log and /var/log/shell.log) with the central record. In the vSphere Client open the host, then Monitor > Tasks and Events and filter by user and time, or run Get-VIEvent -Entity
in PowerCLI. A change visible in vCenter's task history or in the host's configuration but absent from the host logs for the same account and time is the pattern to investigate. This is general practice, not a Broadcom instruction. - Review the accounts that hold the Administrator role on each host (esxcli system permission list) and the SSH and ESXi Shell logins in /var/log/auth.log for the weeks before patching, since the flaw needs administrator rights to be used.
- CISA's KEV entry sets a due date of 11 Nov 2026. Its required action reads: apply mitigations in accordance with vendor instructions, and discontinue use of the product if mitigations are unavailable; the KEV text cites CISA's BOD 26-04 for the patching timeline.
The earliest dated mark of exploitation is CISA's, on 28 Oct 2026, 91 days after disclosure; exploitation may have begun earlier.
Exploitation reported so far
The KEV listing came 91 days after Broadcom's advisory. KEV lists ransomware campaign use as Unknown. No public report names the actor, the operations that were hidden or the attack that used it. Broadcom's advisory does not mention exploitation.
A low CVSS score does not make this harmless in an incident. An unlogged administrator action is useful to someone who has already taken over an ESX administrator account, because it hides what they did from the host's logs. Neither CISA nor Broadcom describes the attack that used it.
Why known-exploited lists settle it
The CVSS score of 2.7 and the high privilege requirement would put this at the back of a queue ordered by CVSS score, and the flaw leaves no log trail to search. The KEV listing and CISA's SSVC entry (exploitation: active) are the only evidence of use, so a known-exploited check is what raises it. The build number from esxcli system version get then tells you which hosts to patch. See known-exploited lists for what the method proves and misses.
Related pages
Sources
- CVE-2026-41709: NVD record, read 19 Nov 2026
- CVE-2026-41709: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
- CVE-2026-41709: Broadcom security advisory VMSA-2026-0006 (vendor advisory, response matrix), read 19 Nov 2026
- CVE-2026-41709: Broadcom KB449886, VMware Telco Cloud response to VMSA-2026-0006, read 19 Nov 2026
- CVE-2026-41709: Broadcom KB344935, Async Patch listing of ESX builds for VCF 5.2.x, read 19 Nov 2026
Last reviewed 19 Nov 2026.