CVE-2026-41709: Broadcom VMWare ESX Insufficient Logging Vulnerability
VMware ESX has an insufficient logging flaw (CWE-778): a malicious administrator can perform certain operations without them being logged. Broadcom fixed it in ESX 9.1.x, 9.0.x and 8.0 U3j, and VCF 5.2.4. CISA added it to the Known Exploited Vulnerabilities catalog on 28 October 2026. Federal agencies must act by 11 November 2026.
Published Jul 30, 2026 · Updated Oct 29, 2026 · Analysis Oct 29, 2026
What an attacker can do
The flaw lets an administrator on ESX carry out some operations that leave no log entry. It does not give an attacker admin rights. The CVSS 3.1 score is 2.7 (low): network attack, high privileges required, and low integrity impact only. Broadcom's advisory gives no further detail on which operations are unlogged.
The practical danger is to forensics. An attacker who already holds ESX administrator rights, for example through stolen credentials or another flaw, can hide actions from the host's logs. That makes incident response and audit harder. CISA's listing means exploitation has been seen, and CISA ties its required action to its forensics triage requirements. The sources I read do not describe the attacks or the actors, and the entry is not marked as used in ransomware campaigns.
Who is affected
Per Broadcom advisory VMSA-2026-0006, CVE-2026-41709 affects ESX 9.1.x, 9.0.x, 8.0 (before U3j), VMware Cloud Foundation 5.x (before 5.2.4) and Telco Cloud Platform 5.0.x and 5.1.x. The advisory does not list ESX 7.0 for this CVE. The advisory does not explain how to check the version. Compare your installed build with the fixed builds in the advisory, using Broadcom's product documentation or the host client.
How to fix it
Install the fixed build for your line, as given in the Broadcom bulletin. Patches are cumulative.
- ESX 9.1.x: ESXi-9.1.0.0-25370933
- ESX 9.0.x: ESXi-9.0.2.0100-25595025
- ESX 8.0: ESXi80U3j-25429389 (8.0 U3j)
- VMware Cloud Foundation 5.x: 5.2.4
- Telco Cloud Platform 5.0.x and 5.1.x: KB449886
Broadcom lists no workarounds. CISA's required action is to apply mitigations per vendor instructions and meet BOD 26-04 and CISA's forensics triage requirements, or to stop using the product if mitigations are unavailable. The due date is 2026-11-11 and binds US federal agencies.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
How to tell if you were hit
By design this flaw leaves gaps in logs, so absence of entries proves little. Review ESX administrator accounts and recent logins, and compare host logs with logs forwarded to a central syslog server, since a remote copy is harder to alter on the host. Look for configuration changes not matched by a log entry. CISA asks organizations to follow its forensics triage requirements. The sources give no specific indicators.
Original advisory
From the National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
VMware ESX contains an insufficient logging vulnerability. A malicious administrator could exploit this issue to perform certain operations without them being logged.
Questions
- Is CVE-2026-41709 exploited in the wild?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 28 October 2026. It is not marked as used in ransomware campaigns.
- Does it give an attacker control of ESX?
No. It needs administrator privileges first. The flaw only lets certain operations run without being logged, so it hides actions.
- Why is a low-severity bug in the KEV catalog?
KEV lists flaws with evidence of exploitation, whatever the CVSS score. This one scores 2.7 but helps hide attacker activity.
- Is there a workaround?
Broadcom lists none. Patch, or follow CISA's instruction to stop using the product if mitigations are unavailable.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
Coverage on the Beam blog
More Broadcom vulnerabilities
All Broadcom entriesCVE-2026-123890
VMWare vCenter Authentication Bypass Using an Alternate Path or Channel Vulnerability
critical9.8ExploitedNov 19, 2026CVE-2026-59310
Broadcom VMware vCenter Path Traversal Vulnerability
critical9.8ExploitedJul 30, 2026CVE-2026-22719
Broadcom VMware Aria Operations Command Injection Vulnerability
high8.1ExploitedFeb 25, 2026CVE-2025-41244
Broadcom VMware Aria Operations and VMware Tools Privilege Defined with Unsafe Actions Vulnerability
high7.8ExploitedSep 29, 2025CVE-2025-1976
Broadcom Brocade Fabric OS Code Injection Vulnerability
high6.7ExploitedApr 24, 2025CVE-2024-37079
Broadcom VMware vCenter Server Out-of-bounds Write Vulnerability
critical9.8ExploitedJun 18, 2024
