CVE-2026-126406
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 …
Impact
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.
An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data or systems being changed.
Affected products · Bytecodealliance
| Product | Affected versions |
|---|---|
| Wasmtime | before 36.0.20 from 37.0.0 before 48.0.8 from 49.0.0 before 49.0.5 from 50.0.0 before 50.0.1 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-h4wp-g4x3-7398
- https://www.vulncheck.com/advisories/wasmtime-before-36.0.20-http-request-smuggling-via-wasi-http-p2-content-length
- https://github.com/advisories/GHSA-xhgr-wvjp-62fm
- https://nvd.nist.gov/vuln/detail/CVE-2026-126406