VMware ESX contains an insufficient logging vulnerability. A malicious administrator could exploit this issue to perform certain operations without them being logged.
CVE-2026-41709
Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-07-30. a secondary CVSS source baseline 2.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.7
- EG Score
- 2.7(high)
- EG Risk
- 12(Track)EG Risk 12/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity27% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
July 30, 2026
References (1)
Vendor Advisories for CVE-2026-41709(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- GCP-2026-051Google Cloud Security BulletinsCritical
GCP-2026-051 — Published: 2026-07-31Description Description Severity Notes Per advisory VMSA-2026-0006, multiple vulnerabilities in VMware ESXi, and…
- GHSA-vpqj-56x2-gp9pGitHub Security AdvisoriesLow
VMware ESX contains an insufficient logging vulnerability. A malicious administrator could...
- GCP-2026-050Google Cloud Security BulletinsCritical
GCP-2026-050 — Published: 2026-07-29Description Description Severity Notes Per advisory VMSA-2026-0006, multiple vulnerabilities in VMware ESXi, and…
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 19:09 UTCGHSA enrichment
- 2026-07-30 16:29 UTCEG score recompute
- 2026-07-30 16:28 UTCGHSA enrichment
- 2026-07-30 15:39 UTCEG score recompute
- 2026-07-30 15:39 UTCGHSA enrichment
- 2026-07-30 14:29 UTCEG score recompute
- 2026-07-30 13:21 UTCEG score recompute
- 2026-07-30 13:21 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-41709?
When was CVE-2026-41709 disclosed?
Is CVE-2026-41709 actively exploited?
What is the CVSS score of CVE-2026-41709?
How do I remediate CVE-2026-41709?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-41709
Is Your Infrastructure Affected by CVE-2026-41709?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.