CriticalCVE-2026-41709

    ESX insufficient logging vulnerability (CVE-2026-41709)

    Published Last modified In CISA KEV since Sources: Vmware Vmsa, BSI, CVE.org, pwn.watch

    Share

    What is affected, what to do

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

    The vulnerability is being actively exploited; treat it as a priority. Update VMware Cloud Foundation to version 5.2.4. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • VMware Cloud Foundation eq 9.1.x.x..9.1.x.x
    • VMware Cloud Foundation eq 9.0.x.x..9.0.x.x
    • VMware Cloud Foundation lt 5.x..5.2.4
    • VMware vSphere Foundation eq 9.1.x.x..9.1.x.x
    • VMware vSphere Foundation eq 9.0.x.x..9.0.x.x
    • VMware ESX gte 9.1.x.x..*
    • VMware ESX gte 9.0.x.x..*
    • VMware ESX gte 8.0..*
    • VMware Telco Cloud Platform eq 5.1.x..5.1.x
    • VMware Telco Cloud Platform eq 5.0.x..5.0.x
    Fixed in
    • VMware Cloud Foundation 5.2.4

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    2.7

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    2.7

    CVSS v3

    Severity Low on the scale from 0 to 10.

    Source: Vmware Vmsa, BSI, CVE.org, pwn.watch

    0.7 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 52.9

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    157.14 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    2.7 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    2.7
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.7 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    52.9
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 28 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-778

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw requires existing administrative privileges and has minimal technical impact in isolation. Its presence on KEV shows that attackers who have already compromised hypervisors actively use it to cover their tracks: it serves anti-forensics and stealthy persistence, not initial access. That makes it most relevant to large vSphere/VCF estates, telco clouds and critical-infrastructure operators, whose NIS2 evidence obligations and incident-response capability depend on complete hypervisor audit trails. CISA does not flag known ransomware use. Patch in an accelerated regular maintenance window, and raise the priority to high with a forensic host review if admin credentials may be compromised or the management network is poorly segmented.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Patch: Use the relevant Broadcom security advisory (VMSA) for ESX 8.0, 9.0.x and 9.1.x, plus Cloud Foundation and Telco Cloud Platform. The context lists VMware Cloud Foundation 5.2.4 as the fixed release for the 5.x line. For every other product line, a patch is available from the vendor — check the vendor advisory for the exact version.
      • Review privileged accounts: Inventory every ESX root account, local admin and vCenter admin (administrator@vsphere.local, SSO admin group members). Disable orphaned accounts and rotate credentials immediately, especially after staff changes or contractor access.
      • Get logs off the host: Confirm Syslog.global.logHost on every host points to a central collector, preferably over TLS on 6514/tcp. A malicious administrator can tamper with logs that exist only on the host.
      • Close shell access: Disable SSH (22/tcp) and ESXi Shell on all hosts unless they are actively needed. Enable Lockdown Mode (normal or strict).
      • Capture a baseline: Export each host's current configuration as a reference for later drift analysis: esxcli system settings advanced list, esxcli software vib list and esxcli system account list.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Make management interfaces (443/tcp, 902/tcp, 22/tcp, 5989/tcp CIM) reachable only from a dedicated admin VLAN or from PAM jump hosts with session recording. Drop all other east-west traffic to the vmk0 network.
      • IAM / least privilege: Do not join ESX hosts directly to the production Active Directory. Use a separate admin domain or an IdP with MFA instead. Apply minimal roles and enforce four-eyes approval for host-level administration in vCenter.
      • Independent logging: Enable audit records on ESX 8.0 and later (esxcli system auditrecords local enable / remote enable). Back them with vCenter events and network telemetry, because host logs alone cannot be trusted.
      • Host hardening: Set VMkernel.Boot.execInstalledOnly=TRUE, enable UEFI Secure Boot and TPM attestation, and set the VIB acceptance level to at least PartnerSupported. This makes it harder to sideload unsigned tooling.
      • Configuration enforcement: Lock logging-related settings (Syslog.global.*, Config.HostAgent.log.level) via Host Profiles or vSphere Configuration Profiles. Any drift should raise an alarm.

    3. Runbook step 3

      Detection rules

      • Log gaps (SIEM): Flag hosts that stop sending syslog for more than N minutes while vCenter still reports them connected. Example SPL: | tstats latest(_time) as last where index=esxi by host | where now()-last>900.
      • vCenter vs. host reconciliation: Treat host-level changes with no matching vCenter task or hostd.log entry as suspicious. This covers VM power events, VIB installs and account changes, and usually points to direct host access or unlogged operations.
      • Logging tampering: Search /var/log/shell.log, hostd.log and vobd.log for esxcli system syslog config set, changes to Syslog.global.logHost, or auditrecords ... disable. Sigma shape: logsource: esxi | selection: CommandLine|contains: ['syslog config set','auditrecords','logHost'].
      • Logins from outside jump hosts: Use Zeek conn.log or firewall logs to find SSH or HTTPS sessions into the ESX management network from sources that are not approved admin jump hosts. Correlate with root logins in auth.log.
      • Baseline drift: Regularly compare esxcli software vib list and the local account list against the saved baseline. New CommunitySupported VIBs or new local accounts point to covert persistence.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

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

    Source: vmware_vmsa, BSI WID Portal, BSI CSAF, NVD (NIST), CISA KEV Catalog, cvelistv5, pwn.watch

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    VMwareCloud Foundation
    • 9.0.x.x
    • 9.1.x.x
    • 5.x – < 5.2.4
    • —
    • —
    • 5.2.4
    VMwareESX
    • ≥ 9.0.x.x
    • ≥ 9.1.x.x
    • ≥ 8.0
    • —
    • —
    • —
    VMwareTelco Cloud Platform
    • 5.1.x
    • 5.0.x
    • —
    • —
    VMwarevSphere Foundation
    • 9.0.x.x
    • 9.1.x.x
    • —
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Othervmwareesxi8.0
    Othervmwareesxi—

    Weakness classes (CWE)

    • CWE-778Insufficient Logging

      Base

      When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.

      Entry at MITRE CWE-778

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • support.broadcom.comVMSA-2026-0006: VMware ESX, vCenter, Workstation, and Fusion updates address multiple vulnerabilitiespwn-watch, Vendor advisory
    • pwn.watchpwn.watch: VMware ESX logging bypass (CVE-2026-41709) added to CISA KEV: admins can act without being loggedpwn-watch
    • cisa.govCISA Adds Two Known Exploited Vulnerabilities to Catalogpwn-watch
    • NVD (NIST)CVE-2026-41709 Detailpwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41709government-resource, US government resource
    • crowdstrike.comCrowdStrike 2026 Legal Threat Landscape Report: eCrime Leads Attacks, China Activity Intensifiespwn-watch
    • thehackernews.comChina-Linked Hackers Exploited VMware ESX Zero-Day to Reduce Audit Trail Visibilitypwn-watch

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Reanalysis by NVDNVD

      Product mapping changed:
      • VMware ESXi (9.0.0 – before 9.0.2.0100; 54 individual versions)
      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationchanged
      AND OR *cpe:2.3:o:vmware:esxi:8.0:-:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3h:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3i:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:*:*:*:*:*:*:*:* versions from (including) 9.0.0 up to (excluding) 9.0.2.0100 *cpe:2.3:o:vmware:esxi:*:*:*:*:*:*:*:* versions from (including) 9.1.0.0 up to (excluding) 9.1.0.0300 OR cpe:2.3:a:vmware:cloud_foundation:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2.4 cpe:2.3:a:vmware:telco_cloud_platform:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2
      AND OR *cpe:2.3:o:vmware:esxi:8.0:-:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3h:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3i:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:*:*:*:*:*:*:*:* versions from (including) 9.0.0 up to (excluding) 9.0.2.0100 OR cpe:2.3:a:vmware:vsphere_foundation:-:*:*:*:*:*:*:* cpe:2.3:a:vmware:cloud_foundation:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2.4 cpe:2.3:a:vmware:telco_cloud_platform:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2
      Product configurationchanged
      AND OR *cpe:2.3:o:vmware:esxi:8.0:-:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3h:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3i:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:*:*:*:*:*:*:*:* versions from (including) 9.0.0 up to (excluding) 9.0.2.0100 *cpe:2.3:o:vmware:esxi:*:*:*:*:*:*:*:* versions from (including) 9.1.0.0 up to (excluding) 9.1.0.0300 OR cpe:2.3:a:vmware:cloud_foundation:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2.4 cpe:2.3:a:vmware:telco_cloud_platform:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2
      AND OR *cpe:2.3:o:vmware:esxi:8.0:-:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3h:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3i:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:*:*:*:*:*:*:*:* versions from (including) 9.0.0 up to (excluding) 9.0.2.0100 OR cpe:2.3:a:vmware:vsphere_foundation:-:*:*:*:*:*:*:* cpe:2.3:a:vmware:cloud_foundation:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2.4 cpe:2.3:a:vmware:telco_cloud_platform:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2

      Source identifier: nvd@nist.gov

    2. Initial analysis by NVDNVD

      Newly listed as affected:
      • VMware ESXi (9.0.0 – before 9.0.2.0100; 9.1.0.0 – before 9.1.0.0300; 27 individual versions)
      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationadded
      —
      AND OR *cpe:2.3:o:vmware:esxi:8.0:-:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_1:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:a:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3b:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3c:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_2f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3d:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3e:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3f:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3g:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3h:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:8.0:update_3i:*:*:*:*:*:* *cpe:2.3:o:vmware:esxi:*:*:*:*:*:*:*:* versions from (including) 9.0.0 up to (excluding) 9.0.2.0100 *cpe:2.3:o:vmware:esxi:*:*:*:*:*:*:*:* versions from (including) 9.1.0.0 up to (excluding) 9.1.0.0300 OR cpe:2.3:a:vmware:cloud_foundation:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2.4 cpe:2.3:a:vmware:telco_cloud_platform:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.2
      Reference typeadded
      —
      VMware: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 Types: Vendor Advisory
      Reference typeadded
      —
      CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41709 Types: US Government Resource

      Source identifier: nvd@nist.gov

    3. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: no

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentremoved
      {"id":"CVE-2026-41709","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-28T19:50:06.869680Z"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2026-41709","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-28T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    4. CISA KEV entry updated9119a7d8…

      4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Date Addedadded
      —
      2026-10-28
      Due Dateadded
      —
      2026-10-28
      Required Actionadded
      —
      2026-10-28
      Vulnerability Nameadded
      —
      2026-10-28

      Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

    5. Record modifiedvmware.com

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017
      Referenceremoved
      https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017
      —

      Source identifier: security@vmware.com

    Show 2 older changes

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: no

      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41709
      SSVC assessmentremoved
      {"id":"CVE-2026-41709","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-07-30T15:10:06.249329Z"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2026-41709","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-28T19:50:06.869680Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Receivedvmware.com

      CVSS V3.1: AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

      Weakness type: CWE-778

      Description added or changed

      Show 5 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Cloud Foundation, vSphere Foundation, ESX (+1)
      Descriptionadded
      —
      VMware ESX contains an insufficient logging vulnerability. A malicious administrator could exploit this issue to perform certain operations without them being logged.
      CVSSadded
      —
      AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
      Weakness type (CWE)added
      —
      CWE-778
      Referenceadded
      —
      https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017

      Source identifier: security@vmware.com

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-41709
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-41709"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-41709.svg?lang=en" alt="CVE-2026-41709 – NEOSEC Intel" height="20"></a>