RUSTSEC-2026-0421GHSA-H4WP-G4X3-7398
wasi-http p2: outgoing content-length can be invalid or not match body
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 36.0.20, 48.0.8, 49.0.5, 50.0.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Wasmtime's WASI HTTP implementation (p2) does not fully validate the Content-Length header on outgoing requests, so the header can be invalid or differ from the actual body length. This can lead to malformed HTTP messages being sent by Wasm guests that rely on Wasmtime's HTTP support.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-h4wp-g4x3-7398 For more information see the GitHub-hosted security advisory.
Timeline
- Advisory published
- Record last updated
- First seen by cve.now
Affected versions
- wasmtime-wasi-httpcrates.io
From 0.0.0-0 · fixed in 36.0.20; From 37.0.0 · fixed in 48.0.8; From 49.0.0 · fixed in 49.0.5; From 50.0.0 · fixed in 50.0.1