Description
wasmtime-wasi-http in Wasmtime before 36.0.16, 37.0.0 before 48.0.3, and 49.0.0 before 49.0.1 does not enforce the wasi:io/streams check-write allowance for WASIp2 outgoing HTTP bodies, so oversized writes succeed instead of trapping. A malicious guest can pass large buffers to write on outgoing-body resources, holding host allocations for the store's lifetime and exhausting host memory.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| bytecodealliance | wasmtime | < 36.0.16, 37.0.0 – < 48.0.3, 49.0.0 – < 49.0.1 | 36.0.16 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | rust-wasmtime | No fix yet | — |
| Ubuntu 26.04 LTS | rust-wasmtime | No fix yet | — |
| Ubuntu 24.04 LTS | rust-wasmtime | No fix yet | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| crates.io | wasmtime-wasi-http | >= 0.0.0-0, < 36.0.16 · >= 37.0.0, < 48.0.3 · >= 49.0.0, < 49.0.1 | 36.0.16, 48.0.3, 49.0.1 | RUSTSEC-2026-0313 |