Wasmtime request smuggling in WASI HTTP outgoing requests
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime-wasi-http crates.io |
|
|
Original description
The wasmtime-wasi-http p2 implementation in Wasmtime before 36.0.20, 37.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 can send conflicting content-length headers, or ones not matching the body, in outgoing requests. A guest that reuses a received response's headers resource to send a bodyless request can enable request smuggling against non-compliant servers, potentially bypassing embedder destination access controls.
From the CVE record · VulnCheck
References
- github.com/bytecodealliance/wasmtime/security/advisories/GHSA-h4wp-g4x3-7398
- vulncheck.com/advisories/wasmtime-before-36.0.20-http-request-smuggling-via-wasi-http-p2-content-length
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/126xxx/CVE-2026-126406.json
- nvd.nist.gov/vuln/detail/CVE-2026-126406
- crates.io/crates/wasmtime-wasi-http
- rustsec.org/advisories/RUSTSEC-2026-0421.html
- github.com/bytecodealliance/wasmtime/pull/15070