CVE-2026-35195 json
Wasmtime has an out-of-bounds write or crash when transcoding component model strings
published 2026-04-09 7 mo ago modified 2026-10-26 13 d ago also EUVD-2026-21039 , GHSA-394w-hwhg-8vgm , JLSEC-2026-1364 , RUSTSEC-2026-0091
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
Wasmtime is a runtime for WebAssembly. Prior to 24.0.7, 36.0.7, 42.0.2, and 43.0.1, Wasmtime's implementation of transcoding strings between components contains a bug where the return value of a guest component's realloc is not validated before the host attempts to write through the pointer. This enables a guest to cause the host to write arbitrary transcoded string bytes to an arbitrary location up to 4GiB away from the base of linear memory. These writes on the host could hit unmapped memory or could corrupt host data structures depending on Wasmtime's configuration. Wasmtime by default reserves 4GiB of virtual memory for a guest's linear memory meaning that this bug will by default on hosts cause the host to hit unmapped memory and abort the process due to an unhandled fault. Wasmtime can be configured, however, to reserve less memory for a guest and to remove all guard pages, so some configurations of Wasmtime may lead to corruption of data outside of a guest's linear memory, such as host data structures or other guests's linear memories. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.
Patch / fix
- crates.io wasmtime 24.0.7, 36.0.7, 42.0.2, 43.0.1
- julia Wasmtime_jll 45.0.1+0
- bytecodealliance wasmtime 24.0.7, 36.0.7, 42.0.2, 44.0.1
- rust-wasmtime Debian 14 36.0.7+dfsg-1
debian advisories DEBIAN-CVE-2026-35195
- github.com/bytecodealliance/wasmtime#13026 pull request
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-2026-35195 updated cvss 6.3
Wasmtime: Wasmtime: Data corruption and potential arbitrary code execution via unvalidated memory reallocation
-
Red Hat Connectivity Link 1 redhat-user-workloads/api-management-tenant/rhcl-1-3-wasm-shim Red Hat Enterprise Linux 10 virt-firmware-rsaffected: workaround, 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
- 6 mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/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 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| OSV | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | wasmtime | <24.0.7 >=25.0.0, <36.0.7 >=37.0.0, <42.0.2 >=43.0.0, <43.0.1 >=0.0.0-0, <24.0.7 |
24.0.7 36.0.7 42.0.2 43.0.1 |
| julia | Wasmtime_jll | <45.0.1+0 |
45.0.1+0 |
Affected products
- bytecodealliance wasmtime
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/bytecodealliance/wasmtime/pull/13026
web
-
github.com
/bytecodealliance/wasmtime/security/advisories/GHSA-394w-hwhg-8vgm
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-35195
advisory, web
-
github.com
/bytecodealliance/wasmtime
package
-
rustsec.org
/advisories/RUSTSEC-2026-0091.html
web, advisory
-
github.com
/advisories/GHSA-394w-hwhg-8vgm
web
-
crates.io
/crates/wasmtime
package
Sources
- CVE List CVE-2026-35195
- GitHub Advisory GHSA-394w-hwhg-8vgm
- NVD CVE-2026-35195
- OSV JLSEC-2026-1364
- OSV RUSTSEC-2026-0091
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.