CVE-2026-35195 Wasmtime has an out-of-bounds write or crash when transcoding component model strings
A guest component can trigger an out-of-bounds write in Wasmtime, potentially causing host crashes or arbitrary memory corruption.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-35195?
CVE-2026-35195 is a medium-severity memory corruption vulnerability in bytecodealliance wasmtime, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-787
Which versions are affected by CVE-2026-35195?
9 open source packages ship an affected version, including wasmtime. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
wasmtime crates.io | All versions | 24.0.7 |
wasmtime crates.io | All versions | 24.0.7 |
wasmtime crates.io | From 0.0.0-0 | 24.0.7, 36.0.7, 42.0.2, 43.0.1 |
wasmtime crates.io | From 25.0.0 | 36.0.7 |
wasmtime crates.io | From 25.0.0 | 36.0.7 |
wasmtime crates.io | From 37.0.0 | 42.0.2 |
3 more packages
wasmtime crates.io | From 37.0.0 | 42.0.2 |
wasmtime crates.io | From 43.0.0 | 43.0.1 |
wasmtime crates.io | From 43.0.0 | 43.0.1 |
Products include Bytecodealliance Wasmtime.
How do I fix CVE-2026-35195?
Upgrade wasmtime to a fixed version for your release line: 24.0.7, 36.0.7, 42.0.2 or 43.0.1.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-35195 being exploited?
There is no known exploitation of CVE-2026-35195 in the wild and no public exploit code.
Other vulnerabilities in bytecodealliance wasmtime
- CVE-2026-34971 Wasmtime miscompiled guest heap access enables sandbox escape on aarch64 Cranelift
- CVE-2026-34987 Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access
- CVE-2022-39393 Wasmtime vulnerable to data leakage between instances in the pooling allocator
- CVE-2022-24791 Use after free in Wasmtime
- CVE-2026-47261 Wasmtime: WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction
Sources
Also known as DEBIAN-CVE-2026-35195, GHSA-394w-hwhg-8vgm, JLSEC-2026-1364, RUSTSEC-2026-0091, UBUNTU-CVE-2026-35195.