CVE-2026-35195 Wasmtime has an out-of-bounds write or crash when transcoding component model strings

Medium 6.1 Published Updated

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.

PackageAffectedFixed in
wasmtime crates.ioAll versions24.0.7
wasmtime crates.ioAll versions24.0.7
wasmtime crates.ioFrom 0.0.0-024.0.7, 36.0.7, 42.0.2, 43.0.1
wasmtime crates.ioFrom 25.0.036.0.7
wasmtime crates.ioFrom 25.0.036.0.7
wasmtime crates.ioFrom 37.0.042.0.2
3 more packages
wasmtime crates.ioFrom 37.0.042.0.2
wasmtime crates.ioFrom 43.0.043.0.1
wasmtime crates.ioFrom 43.0.043.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.

Sources

Also known as DEBIAN-CVE-2026-35195, GHSA-394w-hwhg-8vgm, JLSEC-2026-1364, RUSTSEC-2026-0091, UBUNTU-CVE-2026-35195.

Is CVE-2026-35195 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free