nday
CVE-2026-41709

ESX insufficient logging vulnerability

Broadcom / VMware ESX · VMware / Cloud Foundation, vSphere Foundation, ESX, Telco Cloud Platform

Added to KEV 90 days after disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

network
AV:N in CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N (CVSS 3.1) from the CNA vmware
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N (CVSS 3.1) from the CNA vmware
VMware ESXi
CPE names NVD's analysts give as vulnerable: o:vmware:esxi
virtualization / containers
CPE names NVD's analysts give as vulnerable: o:vmware:esxithe product type of VMware ESXi in nday's product registry
stage
KEV
disclosed
disclosure → KEV
T+90d KEV is date-only
cvss
2.7 LOW v3.1
KEV due date
2026-11-11

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
07-30T12:45Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
≤ 10-28, inferred from KEV
KEVKEV
10-28, date only

Summary

VMware ESX contains an insufficient logging vulnerability. A malicious administrator could exploit this issue to perform certain operations without them being logged.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:H
High: administrative or similar privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

CVSS 3.1 vector from the CVE record, scored by the CNA vmware.

Event log

+DISdisclosed

CVE record published by vmware. CVSS 2.7, low. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 17915,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-41709",
  "occurred_at": "2026-07-30T12:45:02.292Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41709",
      "date_added": "2026-10-28"
    },
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N",
      "version": "3.1",
      "base_score": 2.7,
      "base_severity": "LOW"
    },
    "ssvc": {
      "timestamp": "2026-10-28T00:00:00+00:00",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2026-07-30T12:45:02.292Z",
    "assigner_short_name": "vmware"
  }
}
2026-10-28date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2026-11-11. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 18,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2026-10-28T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-778"
    ],
    "notes": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 ; ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-41709",
    "product": "VMware ESX",
    "due_date": "2026-11-11",
    "precision": "day",
    "date_added": "2026-10-28",
    "vendor_project": "Broadcom",
    "forensic_triage": "No",
    "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.",
    "vulnerability_name": "Broadcom VMWare ESX Insufficient Logging Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2026-10-28inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.