Ad · Leaderboard 728×90

CVE-2026-115889

9.9Critical

Published 23 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

9.9Critical
Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None
Impact
Full C/I/A compromise
Weakness
CWE-197, CWE-843

Impact

Attackers with permission to supply or run WebAssembly can escape the Wasm sandbox to execute arbitrary code or corrupt host memory. They only need the ability to load a crafted Wasm module into the runtime.

Root cause

The Cranelift compiler backend silently overflows bit-packed SSA value indices in release builds during compilation of large functions, causing IR value confusion and miscompilation.

Affected systems

Wasmtime versions prior to 36.0.19 and versions prior to 43.0.0 using the Cranelift backend

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Fix & remediation

Upgrade Wasmtime to version 36.0.19 or 43.0.0 or later. No interim mitigation is documented, so prioritize patching before running untrusted Wasm modules.

shell
$ cargo update -p wasmtime

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

Wasmtime is a runtime for WebAssembly. Prior to 36.0.19 and 43.0.0, the Cranelift compiler backend bit-packs SSA value indices in a way that can silently overflow in release builds when compiling a sufficiently large or specially crafted Wasm function with many SSA values. The overflow can make Cranelift reference incorrect IR values, causing arbitrary miscompilation, type confusion, and other attacker-controlled effects that may escape the Wasm sandbox on any architecture using the default Cranelift backend. This issue is fixed in versions 36.0.19 and 43.0.0.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-115889

Ad · Sticky 320×50 / 728×90