Blog
VMware ESX KEV at CVSS 2.7: insufficient logging is still an engagement problem
CISA added CVE-2026-41709 to KEV on 28 Oct 2026: VMware ESX insufficient logging (CVSS 2.7) that lets a malicious administrator hide certain operations. Operator triage for low-score KEV, audit-gap evidence, and not conflating VMSA Critical siblings.
KEV · Operator triage
On 28 Oct 2026, CISA added CVE-2026-41709 to KEV beside Fragnesia: insufficient logging in Broadcom VMware ESX. Broadcom’s VMSA-2026-0006 rates it Low (CVSS 2.7) — a malicious administrator can perform certain operations without them being logged. No workaround.
This is not an unauthenticated hypervisor RCE finding. The operator problem is evidence integrity after someone already has ESX admin. Same advisory bundle also ships Critical vCenter and ESX issues (CVE-2026-59309 / 59310 / 47876) — do not collapse the whole VMSA into one CVSS number, and do not confuse this KEV with Fragnesia from the same CISA day.
Use VMSA-2026-0006 for build strings. This post is engagement sequencing.
Snapshot
| Field | Value |
|---|---|
| CVE | CVE-2026-41709 |
| Product | VMware ESX / ESXi (also called out under VCF / vSphere Foundation / Telco Cloud Platform matrices) |
| Class | Insufficient logging (CWE-778) |
| CVSSv3.1 (vendor) | 2.7 (AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N) |
| Auth / position | High privileges — malicious administrator (not guest-to-host by itself) |
| Impact | Certain admin operations omitted from audit logs (anti-forensics / detection gap) |
| Workarounds | None |
| KEV added | 2026-10-28 |
| Federal due (verify catalog) | 2026-11-11 |
| Forensic triage (BOD 26-04) | No on the KEV entry — still an evidence problem for anyone who trusts ESX audit logs |
| Same-day KEV sibling | CVE-2026-46300 (Fragnesia) — different stack |
| Reporter (vendor ack) | Ian Barton, CrowdStrike |
Fixed builds for 41709 (first fixed — verify on VMSA)
| Line | Fixed version (VMSA response matrix) |
|---|---|
| ESX 9.1.x | ESXi-9.1.0.0-25370933 |
| ESX 9.0.x | ESXi-9.0.2.0100-25595025 |
| ESX 8.0 | ESXi80U3j-25429389 |
| VCF 5.x ESX | 5.2.4 (see async patching KB88287) |
| Telco Cloud Platform ESX 5.0.x / 5.1.x | Per KB449886 |
Patches are cumulative on later trains — prefer the current vendor-recommended build on your branch, not only the first fixed string.
Why low CVSS still jumps mid-engagement
On authorized assessments and IR-adjacent work:
- Scanner queues sorted by CVSS will bury 2.7 under noise while KEV says active exploitation
- "We reviewed Criticals only" can leave hypervisor audit blind spots after a real admin compromise
- Clean ESX logs are weaker evidence on unpatched builds — absence of events is not absence of action
Industry noise says "another VMware Critical." Engagement state asks: which ESX build, who already has admin, and which sibling CVEs from VMSA-2026-0006 are also in ROE?
Triage questions
- In ROE? ESXi / vSphere / VCF hypervisor management authorized?
- Exact build? Against the 41709 matrix above — not "we are on 8.0 U3."
- Admin already held? By you (authorized) or by an unknown party? 41709 does not create admin; it hides some of what admin did.
- Sibling Criticals in scope? vCenter auth bypass / directory traversal (59309 / 59310) and VMXNET3 host escape (47876) are different findings with different evidence bars.
- What do you pause? Unfinished AD/web paths with evidence deserve a clean pause note — do not abandon them because a Low KEV named ESX.
Operator path
Loading diagram…
Evidence worth capturing
- Exact ESXi build / image profile / VIB set before and after patch
- Whether management interfaces are reachable from in-scope networks
- If IR-authorized: do not conclude "no admin abuse" from ESX audit silence alone on vulnerable builds — correlate vCenter events, external syslog, network telemetry, and guest-side evidence
- Explicit separation in notes: logging CVE vs any Critical sibling you actually tested
Client-facing remediations (short)
- Patch ESX to a fixed build on your train (table above; verify on VMSA-2026-0006)
- Restrict who can obtain ESX / vCenter admin; management plane on trusted networks only (hardening, not a substitute for the patch)
- After suspected compromise on a vulnerable host: assume audit gaps; use out-of-band sources and rebuild discipline where IR requires it
- If the environment still needs the Critical fixes from the same VMSA, schedule those as their own change windows with their own evidence
What not to write
- "CVSS 2.7 = ignore" when the CVE is on KEV with active exploitation
- "Unauthenticated ESXi RCE" for 41709 — vendor path is malicious administrator + missing logs
- Bundling 41709 with 59309 / 59310 / 47876 as one finding
- Completeness claims ("all hypervisors checked") without build inventory
- Invented attribution or ransomware labels (KEV ransomware field: Unknown)
Primary sources: CISA KEV alert (28 Oct 2026), VMSA-2026-0006 / advisory 38017, and NVD CVE-2026-41709. Re-verify fixed builds on the Broadcom advisory before you file.