CVE-2026-35186: Wasmtime has improperly masked return value from `table.grow` with Winch compiler backend
Impact Wasmtime's Winch compiler backend contains a bug where translating the table.grow operator causes the result to be incorrectly typed. For 32-bit tables this means that the result of the operator, internally in Winch, is tagged as a 64-bit value instead of a 32-bit value. This invalid internal representation of Winch's compiler state compounds into further issues depending on how the value is consumed.
Published Apr 10, 2026
Affected packages
wasmtime
- Ecosystem
- Rust (crates.io)
- Affected
- >= 25.0.0, < 36.0.7
- Fixed in
- 36.0.7
- Check
cargo tree -i wasmtime
wasmtime
- Ecosystem
- Rust (crates.io)
- Affected
- >= 37.0.0, < 42.0.2
- Fixed in
- 42.0.2
- Check
cargo tree -i wasmtime
wasmtime
- Ecosystem
- Rust (crates.io)
- Affected
- = 43.0.0
- Fixed in
- 43.0.1
- Check
cargo tree -i wasmtime
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Wasmtime's Winch compiler backend contains a bug where translating the table.grow operator causes the result to be incorrectly typed. For 32-bit tables this means that the result of the operator, internally in Winch, is tagged as a 64-bit value instead of a 32-bit value. This invalid internal representation of Winch's compiler state compounds into further issues depending on how the value is consumed.
One example can be seen when the result of table.grow is used as the address of a load operation. The load operation is tricked into thinking the address is a 64-bit value, not a 32-bit value, which means that the final address to load from is calculated incorrectly. This can lead to a situation where the bytes before the start of linear memory can be loaded/stored to.
The primary consequence of this bug is that bytes in the host's address space can be stored/read from. This is only applicable to the 16 bytes before linear memory, however, as the only significant return value of table.grow that can be misinterpreted is -1. The bytes before linear memory are, by default, unmapped memory. Wasmtime will detect this fault and abort the process, however, because wasm should not be able to access these bytes.
Overall this this bug in Winch represents a DoS vector by crashing the host process, a correctness issue within Winch, and a possible leak of up to 16-bytes before linear memory. Wasmtime's default compiler is Cranelift, not Winch, and Wasmtime's default settings are to place guard pages before linear memory. This means that Wasmtime's default configuration is not affected by this issue, and when explicitly choosing Winch Wasmtime's otherwise default configuration leads to a DoS. Disabling guard pages before linear memory is required to possibly leak up to 16-bytes of host data.
Patches
Wasmtime 43.0.1, 42.0.2, and 36.0.7 have been released with fixes for this issue.
Workaround
There are no workarounds within the Winch compiler backend while using the affected versions. Users of Wasmtime are encouraged either to upgrade to patched versions or, if that is not possible, use the Cranelift compiler backend.
Credited to shumbo, bholley, deian.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Rust (crates.io) vulnerabilities
All Rust (crates.io) entriesCVE-2026-115893
Wasmtime: Cranelift backend on aarch64 can jump to incorrect target on large Wasm `br_table` instruction
critical9.9Oct 28, 2026CVE-2026-115889
Wasmtime: Bit-packing in Cranelift compiler causes silent overflow and miscompilation
critical9.9Oct 23, 2026CVE-2026-115892
Wasmtime: Panic lowering a host-created component model stream into a guest that expects a different payload type
medium5.7Oct 23, 2026CVE-2026-104855
Wasmtime: Preemption and traps during bulk operations enable breaking internal VM state
low2.0Oct 2, 2026CVE-2026-44216
wasmtime has a panic when allocating a table exceeding the size of the host's address space
medium5.9May 7, 2026CVE-2026-34987
Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access
critical9.2Apr 10, 2026
