{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2026-41709 in the wild since at least 28 Oct 2026.","fix":"No fix has been published for CVE-2026-41709 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 11 Nov 2026.","what":"CVE-2026-41709 is a low-severity vulnerability in Vmware Esxi, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41709 and fix it if it is affected.\n\nWhat it is: CVE-2026-41709 is a low-severity vulnerability in Vmware Esxi, published on 30 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2026-41709 in the wild since at least 28 Oct 2026.\n\nAffected product: Vmware Esxi. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41709/ (Markdown: https://insights.sbomify.com/CVE-2026-41709/index.md)","id":"CVE-2026-41709","markdown":"https://insights.sbomify.com/CVE-2026-41709/index.md","name":"CVE-2026-41709","record":{"aliases":["GHSA-vpqj-56x2-gp9p"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"VMware ESX hypervisor","requires_auth":"high_privilege","summary":"A malicious administrator can perform operations without them being logged, bypassing audit trails in VMware ESX environments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"esxi","vendor":"vmware"}],"cvss":{"score":2.7,"severity":"low","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"},"cwes":[{"id":"CWE-778","name":"Insufficient Logging"}],"description":"VMware ESX contains an insufficient logging vulnerability. A malicious administrator could exploit this issue to perform certain operations without them being logged.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Broadcom VMWare ESX Insufficient Logging","id":"CVE-2026-41709","indexable":true,"kev":{"dateAdded":"2026-10-28","dueDate":"2026-11-11","knownRansomwareCampaignUse":"Unknown","product":"VMware ESX","requiredAction":"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.","vendorProject":"Broadcom","vulnerabilityName":"Broadcom VMWare ESX Insufficient Logging Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"vmware:esxi","products":["vmware:esxi"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cache Exhaustion in Stateful Retries leads to Denial of Service","id":"CVE-2026-41710"},"packages":[],"prev":{"headline":"Spring Cloud Sleuth instrumentation of Spring TX DoS vulnerability","id":"CVE-2026-41708"},"products":["Cloud Foundation","ESX","Telco Cloud Platform","vSphere Foundation"],"published":"2026-07-30","related":[{"cvss_score":9.6,"headline":"Information disclosure in VMware ESXi","id":"CVE-2019-5521","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":9.3,"headline":"Use-after-free vulnerability","id":"CVE-2024-22252","kev_date_added":null,"published":"2024-03-05"},{"cvss_score":9.3,"headline":"Cross-site scripting in ESXi","id":"CVE-2020-3955","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":9.3,"headline":"Auth bypass in n/a","id":"CVE-2010-4573","kev_date_added":null,"published":"2010-12-22"},{"cvss_score":8.8,"headline":"Use after free in ESXi, Workstation, Fusion, VMRC and Horizon Client","id":"CVE-2019-5527","kev_date_added":null,"published":"2019-10-10"},{"cvss_score":8.8,"headline":"Memory corruption in VMware ESXi, VMware Workstation, and VMware Fusion","id":"CVE-2018-6981","kev_date_added":null,"published":"2018-12-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["VMware"]},"summary":"A malicious administrator can perform operations without them being logged, bypassing audit trails in VMware ESX environments.","url":"https://insights.sbomify.com/CVE-2026-41709/"}