CVE-2026-35186 Wasmtime has an improperly masked return value from `table.grow` with Winch compiler backend

What is CVE-2026-35186?

CVE-2026-35186 is a medium-severity 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. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, 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. 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. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.

Weakness: CWE-789

Which versions are affected by CVE-2026-35186?

7 open source packages ship an affected version, including wasmtime. It affects 1 product.

Products include Bytecodealliance Wasmtime.

How do I fix CVE-2026-35186?

Upgrade wasmtime to a fixed version for your release line: 36.0.7, 42.0.2 or 43.0.1.

Is CVE-2026-35186 being exploited?

There is no known exploitation of CVE-2026-35186 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 Critical 9.0
• CVE-2026-34987 Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access Critical 9.0
• CVE-2022-39393 Wasmtime vulnerable to data leakage between instances in the pooling allocator High 8.6
• CVE-2022-24791 Use after free in Wasmtime High 8.1
• CVE-2026-47261 Wasmtime: WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction High 7.5

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as DEBIAN-CVE-2026-35186, GHSA-f984-pcp8-v2p7, JLSEC-2026-1363, RUSTSEC-2026-0094, UBUNTU-CVE-2026-35186.