~/exploited / cve-2026-41709
CVE-2026-41709: Broadcom VMware ESX
According to CISA this vulnerability is already used in attacks (added on 28 October 2026).
Key facts
| CVE | CVE-2026-41709 |
|---|---|
| Vendor | Broadcom — VMware ESX |
| Vulnerability | Broadcom VMWare ESX Insufficient Logging Vulnerability |
| Added | 28 October 2026 |
| Deadline (US agencies) | 11 November 2026 |
| Ransomware campaigns | unknown |
Technical data (NVD, FIRST EPSS)
| CVSS base score | 2.7 (low) · CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:NAttack over the network, complexity: low, privileges: high needed, user interaction: none |
|---|---|
| EPSS (exploitation probability) | Probability of exploitation in the next 30 days: 0.69%. Higher than 53.5% of all scored vulnerabilities (as of 18 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks. |
| Weakness type (CWE) | CWE-778 |
| Affected versions | esxi: >= 9.0.0, < 9.0.2.0100 esxi 8.0 |
Description (NVD)
VMware ESX contains an insufficient logging vulnerability. A malicious administrator could exploit this issue to perform certain operations without them being logged.
Patches and vendor advisories
Description (CISA)
Broadcom VMWare ESX contains an insufficient logging vulnerability that could allow a malicious actor with admin access to perform certain operations without being logged.
Required action (CISA)
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.
What admins should do now
- Affected? Check whether Broadcom VMware ESX is in use and which version runs (package manager, admin UI,
--version). - Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
- Review logs back to 28 October 2026: unusual logins, new files, unexpected processes, outbound connections.
- If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.
The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.
Sources
- CISA KEV Catalog
- NVD CVE-2026-41709
- support.broadcom.com/web/ecx/support-content-notification/-/external/content/Sec
- www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-base
- www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizi
- nvd.nist.gov/vuln/detail/CVE-2026-41709
New articles by e-mail
One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).