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.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Fri, 13 Nov 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Wasmtime before 36.0.20 HTTP Request Smuggling via wasi-http p2 Content-Length | |
| First Time appeared |
Bytecodealliance
Bytecodealliance wasmtime |
|
| Weaknesses | CWE-444 | |
| CPEs | cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Bytecodealliance
Bytecodealliance wasmtime |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-13T09:35:44.314Z
Reserved: 2026-11-10T21:32:21.765Z
Link: CVE-2026-126406
No data.
Status : Deferred
Published: 2026-11-13T10:17:45.440
Modified: 2026-11-13T10:17:45.583
Link: CVE-2026-126406
No data.
OpenCVE Enrichment
No data.
Weaknesses