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-115893, RUSTSEC-2026-0379
Wasmtime: Cranelift backend on aarch64 can jump to incorrect target on large Wasm br_table instruction
Summary
When running with the Cranelift compiler backend on an aarch64 target, Wasmtime can compile a Wasm module with more than ~256k targets on one br_table instruction in a way that results in an incorrect conditional branch target. This conditional branch could then jump to arbitrary other code (at an user-controlled offset), leading to arbitrary sandbox escapes.
Impact
Any Wasmtime engine running on aarch64 with default settings can be forced to jump to arbitrary code by a user-controlled Wasm module. All versions of Wasmtime/Cranelift that support aarch64, since the initial release of that support in 2020 (before Wasmtime v1.0), are affected.
Patches
Wasmtime v36.0.19, v48.0.7, and v49.0.4 have been released which all fix 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 48.0.7 (semver)48.0.7
48.0.7cargo update -p wasmtime --precise 48.0.749.0.0, fixed 49.0.4 (semver)49.0.4
49.0.4cargo update -p wasmtime --precise 49.0.4Fix 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