CVE-2025-41237: VMCI integer-underflow vulnerability
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: 17.6.4; 13.6.4 CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
VMware ESXi, Workstation, and Fusion contain an integer-underflow in VMCI (Virtual Machine Communication Interface) that leads to an out-of-bounds write. A malicious actor with local administrative privileges on a virtual machine may exploit this issue to execute code as the virtual machine's VMX process running on the host. On ESXi, the exploitation is contained within the VMX sandbox whereas, on Workstation and Fusion, this may lead to code execution on the machine where Workstation or Fusion is installed.
- weakness
- CWE-787 Out-of-bounds Write
- affected
- VMware Cloud Foundation; VMware vSphere Foundation; VMware ESXi; VMware Workstation; VMware Fusion; VMware Telco Cloud Platform; VMware Telco Cloud Infrastructure
- versions
- No affected-version range in held sources.
- fixed in
- 17.6.4; 13.6.4
- severity
- 9.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- assigned by
- vmware
- published
- 2025-07-15
check us support.broadcom.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 16 Jul 2025 | 0.00017 | |
| 21 Jul 2025 | 0.00022 | |
| 16 Aug 2025 | 0.00025 | |
| 21 Sep 2025 | 0.00027 | |
| 15 Jun 2026 | 0.00393 | scoring model v2026.06.15 |
| 12 Aug 2026 | 0.0039 | |
| 28 Aug 2026 | 0.00448 | |
| 5 Oct 2026 | 0.00455 | |
| 16 Oct 2026 | 0.00461 |
19 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-10-16 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: 17.6.4; 13.6.4. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-41237', '2026-10-30T23:59:59.999999Z', now());