Plan this weekVulnerabilities

Two critical Wasmtime flaws can let a WebAssembly module escape its sandbox

Bytecode Alliance fixed two critical Wasmtime bugs (CVSS 9.9) on 19 Oct 2026. They matter if your app runs WebAssembly you do not control. Here is who is affected and what to update.

How urgent

Plan this week

Who is affected

Software that embeds Wasmtime and runs WebAssembly supplied by someone you do not control (plugins, agent tools, multi-tenant platforms), on Wasmtime before 36.0.19, 37.x to 42.x, or, on ARM64 only, up to 48.0.6 and 49.0.0 to 49.0.3

What to do

If you run WebAssembly from outside parties with Wasmtime, update to 36.0.19, 48.0.7, 49.0.4 or later in your line, then rebuild and redeploy whatever embeds it

Published 26 Oct 2026 · Sources last checked 26 Oct 2026No. 13 / 87

What happened

On 19 October 2026 the Bytecode Alliance published two advisories for Wasmtime, a runtime that runs WebAssembly (Wasm) programs inside a sandboxSandbox A fenced-off area where a program runs with limited access, so if it misbehaves it cannot touch the rest of the system. Tap again to open the glossary. Both are rated Critical, CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary 9.9, and both sit in Cranelift, the part of Wasmtime that turns Wasm into machine code:

  • CVE-2026-115889 is a bug where Cranelift packs internal indexes into too few bits. In release builds this can overflow silently and produce wrong code, which can cause type confusion. The advisory says it can allow a sandbox escape. It affects any architecture or platform.
  • CVE-2026-115893 is a bug on ARM64 (aarch64) only. A Wasm module with a very large br_table instruction (more than about 256,000 targets) can make the compiler pick a wrong jump target, so the code jumps to arbitrary code at an offset the module controls. The advisory says every version that supports ARM64 has been affected since 2020.

In both cases the attacker needs to supply the Wasm module that your app runs. The advisories list no workarounds, and they do not say whether anyone is exploiting these flaws. We did not find a report of attacks in the sources we read.

Who is affected

This matters if your software embeds Wasmtime and runs WebAssembly that someone else wrote: a plugin system, a tool sandbox for AI agents, a platform where customers upload code. If you only run Wasm you built yourself, an attacker has no way to hand you a malicious module, so the risk is much lower.

Which versions:

  • CVE-2026-115889 (any platform): Wasmtime before 36.0.19, and 37.x to 42.x. Version 43 changed the compiler so it is not affected.
  • CVE-2026-115893 (ARM64 only): Wasmtime before 36.0.19, 37.0.0 to 48.0.6, and 49.0.0 to 49.0.3.

Fixed versions named by the advisories: 36.0.19, 48.0.7 and 49.0.4. A project on 37.x to 42.x is hit by both flaws, so it should move to 48.0.7, 49.0.4 or later.

What to do

  1. Find out whether you use Wasmtime. Look for wasmtime in your Cargo.lock or dependency list, or run wasmtime --version if you use its command line. If you use a platform or product that runs Wasm for you, ask the vendor.
  2. If you run Wasm you do not control, update to 36.0.19 (if you are on the 36 line), 48.0.7, 49.0.4 or a later release.
  3. Rebuild and redeploy. When Wasmtime is a library inside your app, updating a system package changes nothing: the new version only counts after you rebuild and redeploy.
  4. Make a short inventory of which services bundle it, so the next advisory takes minutes, not days.
  5. If you only run your own Wasm, plan the update with your normal releases.

If you build with AI tools

Our advice, not from the advisories: tool sandboxes for AI agents and plugin systems often run third-party code. A sandbox is only as safe as the runtime inside it. Keep the runtime updated, treat every module you did not write as untrusted, and do not give the process running them access to your keys or your production data.

What we could not confirm

We read the two official advisories and one press summary. We have not tested these flaws or checked which products bundle Wasmtime, so we do not name any. The press summary lists a later release, 50.0.0, that the advisories do not mention; we use only the versions the advisories name.

Terms explained in this article

  • CVE: A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug.
  • CVSS score: A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical.
  • Sandbox: A fenced-off area where a program runs with limited access, so if it misbehaves it cannot touch the rest of the system.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks