CVE-2026-115893: Wasmtime: Cranelift backend on aarch64 can jump to incorrect target on large Wasm `br_table` instruction
Wasmtime's Cranelift backend on aarch64 miscompiles a Wasm `br_table` instruction with more than about 256k targets. The branch can land at the wrong place, and the advisory says an attacker-supplied module can use that to escape the sandbox. Fixed in Wasmtime 36.0.19, 48.0.7 and 49.0.4. Hosts that run untrusted Wasm on aarch64 should upgrade first.
Published Oct 28, 2026 · Analysis Oct 29, 2026
What an attacker can do
Cranelift generates the jump table for a Wasm br_table. On aarch64, once one br_table has more than roughly 256,000 targets, the generated conditional branch goes to an incorrect target. The advisory says the jump can land in other code at an offset the module author controls. That breaks the isolation Wasmtime gives to guest code, so the module can run code outside the sandbox.
The attacker needs to get a Wasm module compiled and run by your Wasmtime engine. That is the normal situation for plugin systems, serverless and edge platforms, and any service that runs customer-supplied Wasm. The default settings are affected. Every Wasmtime and Cranelift release that supports aarch64 is affected, back to the first aarch64 support in 2020, before Wasmtime 1.0. Hosts on x86-64 are not named in the advisory. The CVSS vector scores a changed scope with high impact on confidentiality, integrity and availability.
The module must be unusually large, but an attacker who supplies it can build one on purpose. Wasm modules you author yourself and trust carry no such risk.
Who is affected
Wasmtime below 36.0.19, from 37.0.0 up to below 48.0.7, and from 49.0.0 up to below 49.0.4. Only aarch64 hosts with the Cranelift backend are affected. That includes embedders that use the wasmtime Rust crate and tools built on it.
wasmtime --version
cargo tree -i wasmtimeFor language bindings, check which Wasmtime release the binding bundles.
wasmtime
- Ecosystem
- Rust (crates.io)
- Affected
- < 36.0.19
- Fixed in
- 36.0.19
- Check
cargo tree -i wasmtime
wasmtime
- Ecosystem
- Rust (crates.io)
- Affected
- >= 37.0.0, < 48.0.7
- Fixed in
- 48.0.7
- Check
cargo tree -i wasmtime
wasmtime
- Ecosystem
- Rust (crates.io)
- Affected
- >= 49.0.0, < 49.0.4
- Fixed in
- 49.0.4
- Check
cargo tree -i wasmtime
How to fix it
Upgrade to a patched release: Wasmtime 36.0.19, 48.0.7 or 49.0.4, depending on your release line.
cargo update -p wasmtimePin the new version in Cargo.toml if you track a specific line, rebuild and redeploy. Embedders that ship Wasmtime in a binary or container must rebuild it. The advisory names no workaround. Until you upgrade, avoid running untrusted Wasm modules on aarch64 hosts.
How to tell if you were hit
Look for Wasm modules with very large br_table instructions, that is, tens of thousands of branch targets or more, uploaded to or run by your hosts. A dump with wasm-tools print or wasm-objdump -d shows them. The advisory lists no log signature for an exploited sandbox escape. Unexpected crashes or odd behavior of a Wasmtime host process after loading a customer module on aarch64 are worth investigating. Inventory your aarch64 hosts and their Wasmtime versions.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to ilyas-mallah.
Questions
- Does CVE-2026-115893 affect x86-64 hosts?
The advisory describes the bug in the aarch64 backend and names no other architecture. Check the Wasmtime release notes for your platform if you run something else.
- Does it need a special configuration?
No. The advisory says any Wasmtime engine on aarch64 with default settings can be forced to jump to arbitrary code by a user-controlled Wasm module.
- Which versions fix it?
Wasmtime 36.0.19, 48.0.7 and 49.0.4. Pick the one that matches your release line.
- Is it exploited in the wild?
No source says so, and it is not in CISA's KEV catalog.
References
Read for this analysis:
- https://nvd.nist.gov/vuln/detail/CVE-2026-115893
- https://github.com/bytecodealliance/wasmtime/pull/14818
- https://github.com/bytecodealliance/wasmtime/pull/14819
- https://github.com/bytecodealliance/wasmtime/pull/14820
- https://github.com/bytecodealliance/wasmtime/pull/14826
- https://github.com/bytecodealliance/wasmtime/commit/222ff3a65dab9aa7011f8c246937751a0bac5abd
- https://github.com/bytecodealliance/wasmtime/commit/994549891c8a706cb4f2809f9d17b9f67b31e618
- https://github.com/bytecodealliance/wasmtime/commit/e61df1b454be9313d61a5f8de07722a421139bbe
- https://github.com/bytecodealliance/wasmtime/commit/f517bd6e890c7c1291ab9fe05d8cc0c9f11e56aa
- https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.19
- https://github.com/bytecodealliance/wasmtime/releases/tag/v48.0.7
- https://github.com/bytecodealliance/wasmtime/releases/tag/v49.0.4
- https://rustsec.org/advisories/RUSTSEC-2026-0379.html
- https://github.com/advisories/GHSA-mghf-wjfp-p5xm
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More Rust (crates.io) vulnerabilities
All Rust (crates.io) entriesCVE-2026-115889
Wasmtime: Bit-packing in Cranelift compiler causes silent overflow and miscompilation
critical9.9Oct 23, 2026CVE-2026-115892
Wasmtime: Panic lowering a host-created component model stream into a guest that expects a different payload type
medium5.7Oct 23, 2026CVE-2026-104855
Wasmtime: Preemption and traps during bulk operations enable breaking internal VM state
low2.0Oct 2, 2026CVE-2026-44216
wasmtime has a panic when allocating a table exceeding the size of the host's address space
medium5.9May 7, 2026CVE-2026-34987
Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access
critical9.2Apr 10, 2026CVE-2026-35186
Wasmtime has improperly masked return value from `table.grow` with Winch compiler backend
medium6.1Apr 10, 2026
