Exploited VMware ESX insufficient logging flaw added to CISA's KEV catalogue
On 28 October 2026 CISA added CVE-2026-41709, a flaw in Broadcom VMware ESX, to its catalogue of actively exploited vulnerabilities. It lets an actor with administrator access carry out certain operations without them being logged, which matters to any organisation running ESX hypervisors.
What to do now
- Product
- Broadcom VMware ESX
- Affected versions
- —
- CVE
- CVE-2026-41709
The US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-41709, affecting Broadcom's VMware ESX hypervisor, to its Known Exploited Vulnerabilities catalogue on 28 October 2026. The issue is an insufficient logging weakness, classified as CWE-778.
According to the published description, a malicious actor who already holds administrator privileges on an ESX host can perform certain operations that are not recorded in the logs. The flaw does not grant access by itself, but it helps an intruder who is already inside hide part of their activity, making detection and incident investigation harder. The source does not say which operations escape logging.
Broadcom has published security advisory 38017 on its support portal. CISA's entry does not list affected or fixed versions, so administrators need to read the vendor advisory to find out which patches or mitigations are available. CISA also states that it does not know whether the flaw has been used in ransomware campaigns.
US federal civilian agencies must apply the vendor's mitigations by 11 November 2026 under directive BOD 26-04, or stop using the product if no mitigation exists. Other organisations are not bound by that deadline, but it is a useful signal of how urgently to act.
For teams running ESX, a KEV listing means the flaw has been seen exploited in real attacks. Because it requires prior administrator access, it is also a prompt to review who holds those rights and to check that privileged accounts have not been compromised.
What to do now
- Read Broadcom security advisory 38017 and apply the patch or mitigation it describes to your ESX hosts without delay.
- Review which accounts hold administrator rights on your ESX hypervisors and remove or reset any that are not justified.
- Look for signs that administrator accounts have been compromised, bearing in mind that some actions may be missing from ESX logs.
- As general good practice, restrict ESX management interfaces to an isolated management network and forward logs to an external server.