wasmtime
Affected
- introduced
0, fixed36.0.19(semver)
Fixed versions
36.0.19
Fix
- Fixed version
36.0.19cargo update -p wasmtime --precise 36.0.19
Advisory
Also known as: CVE-2026-115889, RUSTSEC-2026-0380
Wasmtime: Bit-packing in Cranelift compiler causes silent overflow and miscompilation
Summary
In Wasmtime prior to v43, the Cranelift compiler backend bit-packs its SSA value indices in a way that can result in silent overflow in release builds, and result in incorrect value references in the IR resulting in arbitrary miscompilation. A very large Wasm function body, or one that is specially crafted to use many SSA values, can use this to force type-confusion or other arbitrary side-effects and escape the sandbox.
Cranelift was changed in Wasmtime v43 to use a full u32 index, with checks if that limit is exceeded, and so is no longer susceptible to this bug.
Impact
A Wasmtime engine with default settings (using the Cranelift backend) on any architecture/platform could experience a sandbox escape from a specially-crafted Wasm module.
Patches
Wasmtime v36.0.19 has been released which fixes this issue.
Critical Basis: The source's own band: CRITICAL
0, fixed 36.0.19 (semver)36.0.19
36.0.19cargo update -p wasmtime --precise 36.0.1937.0.0, fixed 43.0.0 (semver)43.0.0
43.0.0cargo update -p wasmtime --precise 43.0.0Fix 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