Skip to content
Brief Security & Trust ·

Two critical Wasmtime flaws could let hostile code escape its sandbox

Both bugs are fixed in supported releases, but the fix has to reach every program that embeds Wasmtime.

In brief
  • Two flaws in Wasmtime's compiler could let a hostile WebAssembly module break out of its sandbox. Both are rated 9.9 out of 10 and have fixes in supported releases.
  • Wasmtime is built into other software, so each program that uses it needs a rebuild. Ask which of your products embed it.

The Hacker News reported on October 26 that two flaws in Wasmtime, which runs WebAssembly outside browsers, could let a hostile module escape its sandbox. The Bytecode Alliance, its maintainer, rated each flaw 9.9 out of 10 on the CVSS severity scale. Both bugs are in Cranelift, its default compiler. CVE-2026-115889 affects default setups on any platform; CVE-2026-115893 affects only ARM64. The maintainers have reported no attacks.

In CVE-2026-115889, Cranelift before version 43 packed value numbers into 24-bit fields. In release builds, a number too big overflowed silently, so code could point at the wrong value. The sources do not explain the ARM64 flaw or say what an attacker could reach after escaping. Neither flaw was in CISA's Known Exploited Vulnerabilities catalog on October 26. Version 50.0.0 fixes both. The sources list 36.0.19, 48.0.7 and 49.0.4 as fixes for their lines but do not say if each covers both. Other lines, such as 24.x, got no fix.

Risk is highest where outsiders supply modules, because an attacker needs a vulnerable build to compile a module they control. Fastly says its Compute platform runs customer code using Wasmtime. Wasmtime is a library, so a fix reaches a product only after its vendor rebuilds it. Ask vendors and your own teams: is Wasmtime embedded, which line, and rebuilt?

A WebPulse Brief: a short report of an important event, written by the WebPulse Newsroom with AI assistance and checked against the reporting below. When there is more to explain, we follow up with a full story. How we use AI.

Reporting: Bytecode Alliance (Wasmtime project maintainers), via their GitHub security advisory for CVE-2026-115889.