Wasmtime denial of service in WASIp2 outgoing HTTP body writes
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime-wasi-http crates.io |
|
|
Original 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.
From the CVE record · VulnCheck
References
- github.com/bytecodealliance/wasmtime/security/advisories/GHSA-c9gc-w9vx-w86p
- vulncheck.com/advisories/wasmtime-before-36.0.16-37.0.0-before-48.0.3-and-49.0.0-before-49.0.1-memory-exhaustion-dos-via-wasmtime-wasi-http-outgoing-body-write
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/115xxx/CVE-2026-115388.json
- nvd.nist.gov/vuln/detail/CVE-2026-115388
- crates.io/crates/wasmtime-wasi-http
- rustsec.org/advisories/RUSTSEC-2026-0313.html
- github.com/bytecodealliance/wasmtime/pull/14408