wasmtime
Affected
- introduced
0, fixed24.0.7(semver)
Fixed versions
24.0.7
Fix
- Fixed version
24.0.7cargo update -p wasmtime --precise 24.0.7
Advisory
Also known as: CVE-2026-34944, RUSTSEC-2026-0087
Wasmtime segfault or unused out-of-sandbox load with f64x2.splat operator on x86-64
On x86-64 platforms with SSE3 disabled Wasmtime's compilation of the f64x2.splat WebAssembly instruction with Cranelift may load 8 more bytes than is necessary. When signals-based-traps are disabled this can result in a uncaught segfault due to loading from unmapped guard pages. With guard pages disabled it's possible for out-of-sandbox data to be loaded, but this data is not visible to WebAssembly guests.
Details
The f64x2.splat operator, when operating on a value loaded from a memory (for example with f64.load), compiles with Cranelift to code on x86-64 without SSE3 that loads 128 bits (16 bytes) rather than the expected 64 bits (8 bytes) from memory. When the address is in-bounds for a (correct) 8-byte load but not an (incorrect) 16-byte load, this can load beyond memory by up to 8 bytes. This can result in three different behaviors depending on Wasmtime's configuration:
Wasmtime's default configuration is case (2) in this case. That means that Wasmtime, by default, incorrectly executes this
WebAssembly instruction but does not have insecure behavior.
Impact
If signals-based-traps are disabled and guard pages are enabled then guests can trigger an uncaught segfault in the host, likely aborting the host process. This represents, for example, a DoS vector for WebAssembly guests.
This bug does not affect Wasmtime's default configuration and requires signals-based-traps to be disabled. This bug only affects the x86-64 target with the SSE3 feature disabled and the Cranelift backend (Wasmtime's default backend).
Patches
Wasmtime 24.0.7, 36.0.7, 42.0.2, and 43.0.1 have been issued to fix this bug. Users are recommended to update to these patched versions of Wasmtime.
Workarounds
This bug only affects x86-64 hosts where SSE3 is disabled. If SSE3 is enabled or if a non-x86-64 host is used then hosts are not affect. Otherwise there are no known workarounds to this issue.
Medium Basis: The source's own band: MODERATE
0, fixed 24.0.7 (semver)24.0.7
24.0.7cargo update -p wasmtime --precise 24.0.725.0.0, fixed 36.0.7 (semver)36.0.7
36.0.7cargo update -p wasmtime --precise 36.0.737.0.0, fixed 42.0.2 (semver)42.0.2
42.0.2cargo update -p wasmtime --precise 42.0.243.0.0, fixed 43.0.1 (semver)43.0.1
43.0.1cargo update -p wasmtime --precise 43.0.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0