CVE-2025-62711 json
Wasmtime vulnerable to segfault when using component resources
published 2025-07-18 15 mo ago modified 2026-10-12 27 d ago also EUVD-2025-35897 , GHSA-4h67-722j-5pmc , RUSTSEC-2025-0112
- cvss
- 3.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Wasmtime is a runtime for WebAssembly. In versions from 38.0.0 to before 38.0.3, the implementation of component-model related host-to-wasm trampolines in Wasmtime contained a bug where it's possible to carefully craft a component, which when called in a specific way, would crash the host with a segfault or assert failure. Wasmtime 38.0.3 has been released and is patched to fix this issue. There are no workarounds.
Patch / fix
- crates.io wasmtime 38.0.3
- bytecodealliance wasmtime 38.0.3
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-62711 updated cvss 3.7
wasmtime: Wasmtime vulnerable to segfault when using component resources
-
Red Hat Connectivity Link 1 rhcl-1/wasm-shim-rhel9affected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12 mo ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.1 | CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L |
| CNA | 4.0 | 2.1 | CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | wasmtime | >=38.0.0, <38.0.3 |
38.0.3 |
Affected products
- bytecodealliance wasmtime
Classification
- Weakness
-
- CWE-755 Improper Handling of Exceptional Conditions
References
-
github.com
/bytecodealliance/wasmtime/pull/11592
web, patch
-
github.com
/bytecodealliance/wasmtime/commit/192f2fcdadfec9d0cf6b58548a85a7307450cbf5
web, patch
-
github.com
/bytecodealliance/wasmtime/security/advisories/GHSA-4h67-722j-5pmc
web, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-62711
advisory
-
github.com
/bytecodealliance/wasmtime
package
-
rustsec.org
/advisories/RUSTSEC-2025-0112.html
web, advisory
-
crates.io
/crates/wasmtime
package
Sources
- CVE List CVE-2025-62711
- GitHub Advisory GHSA-4h67-722j-5pmc
- NVD CVE-2025-62711
- OSV RUSTSEC-2025-0112
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.