Exploited CVEs / Broadcom / CVE-2026-41709
CVE-2026-41709
Broadcom VMWare ESX Insufficient Logging Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-11-11 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Broadcom (VMware) Security Advisories, linked below.
Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.
Risk summary
Actively exploited Broadcom VMware ESX vulnerability, Low severity, CVSS v3 2.7. Added to the CISA KEV catalog 2026-10-28.
Updated October 28, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2026-41709
CVE-2026-41709 is an insufficient logging flaw in Broadcom VMware ESX that lets someone who already holds admin access perform certain operations without leaving a log entry. What is unusual is the mismatch: Severity is Low (CVSS 2.7) and EPSS is only 1%, yet CISA added it to KEV on 2026-10-28 as confirmed exploited, which suggests attackers are using it to cover their tracks after gaining admin rights rather than to break in. Any organization running Broadcom VMware ESX is exposed, and the real risk is losing the audit trail you would rely on to scope a hypervisor compromise.
Do this: Apply the Broadcom fix for CVE-2026-41709 to your ESX hosts, and in the meantime forward ESX logs to an external collector and review recent admin activity on hosts for gaps or unexplained changes.
AI-generated from public data, 2026-11-10. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-41709
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2026-41709
- Published
- 2026-10-28
- Last revised
- 2026-10-28
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
The strongest signal is that CISA added CVE-2026-41709 to the KEV catalog on 2026-10-28, which confirms active exploitation regardless of score. EPSS stayed low, rising from 0.3% to 0.8% on 2026-10-29 before easing to 0.7% on 2026-10-30. That small dip is noise, so treat this as a known-exploited flaw and patch it today.
Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.
- 2026-10-28 EPSS first scored at 0.3%; added to the CISA KEV catalog by CISA
- 2026-10-29 EPSS 0.3% to 0.8%
- 2026-10-30 EPSS 0.8% to 0.7%
Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.
From the Senserva blog
- Patch and Vulnerability Intelligence
July 10, 2026 · Kyle, Senserva Dev Team
CISA required action
Federal remediation due date: 2026-11-11 (past due).
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.
Official fix for CVE-2026-41709
The authoritative fix and affected-version list are published by the vendor. Find the VMware ESX advisory on Broadcom (VMware) Security Advisories.
Common questions about CVE-2026-41709
Is CVE-2026-41709 actively exploited?
Yes. CVE-2026-41709 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-10-28, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is <1%.
What is the CISA deadline and required action for CVE-2026-41709?
CISA set the federal remediation due date at 2026-11-11, which has passed; treat any unremediated system as overdue. The verbatim 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.
What fixes CVE-2026-41709?
The authoritative fix is in the vendor advisory: see Broadcom (VMware) Security Advisories for the patched VMware ESX versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2026-41709?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-41709's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).
Scope and sources
- More exploited Broadcom CVEs
All Broadcom exploited CVEs on one page: Broadcom vulnerabilities actively exploited.
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.