CVE-2026-41709
🔴 High In CISA KEVVMware ESX / ESXi, with vSphere Foundation, Cloud Foundation and Telco Cloud Platform downstream · ESX 9.1.x → ESXi-9.1.0.0-25370933 ; 9.0.x → ESXi-9.0.2.0100-25595025 ; 8.0 → ESXi80U3j-25429389 ; Cloud Foundation 5.x below 5.2.4 → 5.2.4 ; vSphere Foundation 9.0 and 9.1 through the ESX builds ; Telco Cloud Platform 5.0.x and 5.1.x through KB449886, which is easy to miss
CVSS (Koffei note)
2.7CVSS (v3.1, CVE List)
2.7EPSS (2026-11-18)
0.689%53.46th percentile
CISA KEV
2026-10-28due 2026-11-11
Exploitation
Yes — CISA KEV since 28/10/2026, federal remediation due 11/11/2026 (SSVC exploitation active, 28/10/2026, technical impact partial ; ransomware use unknown). Exploited as a zero-day in early 2026 by Warp Panda (also Armory Castle, formerly UNC5221, and reported as Clay Typhoon and VerdantBamboo) to reduce audit-trail visibility, alongside edge-device access and a vCenter pivot, deploying BRICKSTORM and SharpStorm and going on to M365 token theft and a rogue MFA device, against US targets with a legal-sector focus. No public PoC. Note the three-month gap between the July 2026 fix and the 28/10/2026 KEV listing Update 30/10/2026: Broadcom still has not published which operations go unlogged, and no advisory revision since July 2026 was found, so the gap in what a SOC can compensate for is unchanged. The attribution firms up: CrowdStrike is the attributing vendor, and the aliases are Armory Castle (formerly UNC5221), Clay Typhoon and VerdantBamboo, with BRICKSTORM and SharpStorm deployed after pivoting to vCenter. SAWFLY and BARECLAW appear in the same coverage but belong to a separate incident and are not part of this.
Timeline
- 30/07/2026CVE record published (CVE List)
- 28/10/2026Added to the CISA KEV catalogue
- 29/10/2026Warp Panda (China-nexus) exploited a VMware ESX logging-bypass flaw as a zero-day
- 30/10/2026VMware ESX logging-bypass flaw added to CISA KEV after China-nexus zero-day use
- 30/10/2026Warp Panda (China-nexus) exploited VMware ESX zero-day against US legal sector
- 02/11/2026VMware ESX logging-bypass flaw added to KEV
- 02/11/2026Warp Panda exploited VMware ESX zero-day to evade audit logging
- 11/11/2026CISA deadline for US federal agencies
Relationships
exploits suspected named in the same story vendor · Select a box to open its page · All relationships
Risk
2.7 Low (v3.1, VMware CNA) — AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N, EPSS 0.689% (52.75th percentile, scored 01/11/2026, down from 0.764%) (CWE-778 insufficient logging) — and it is in CISA KEV anyway, which makes it the clearest example in this report of why a CVSS threshold is not a triage rule. Requires existing administrator access ; the impact is pure anti-forensics, as certain operations go unlogged, and Broadcom has not published which ones, which caps what a SOC can compensate for
Fix
Yes — the builds above (Broadcom advisory 38017, July 2026). No workaround or mitigation was published, the fixes are image builds so each host needs maintenance mode and a reboot, and after patching, the pre-patch logs on any in-scope host should be treated as untrustworthy — which is the whole point of the bug
Official description
VMware ESX contains an insufficient logging vulnerability. A malicious administrator could exploit this issue to perform certain operations without them being logged.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
CWE-778