RUSTSEC-2026-0421Low· 3.7▾ Sunlitwasi-http p2: outgoing content-length can be invalid or not match body
▾ Sunlit zone — Low / medium · no exploitation signal
impact 20.4 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
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.
wasmtime-wasi-http >= 50.0.0, < 50.0.1Upgrade to a patched release:
wasmtime-wasi-http 50.0.1Connected by shared product, vendor, weakness, or advisory.
CVE-2026-121441Low· 3.7`wasi-http`: Guests can add conflicting content lengths to messages
CVE-2026-121440Low· 3.7`wasi-http` p3: forwarded trailers aren't checked against `is_forbidden_header` hook
CVE-2026-121439Medium· 5.3`wasi-http` p3: Guests can set incorrect content-length for spliced response bodies
CVE-2026-119131Medium· 5.3`wasi-http`: Request with long url before query parameter crashes host
CVE-2026-119130NoneGuests can send absolute-form HTTP requests to different hosts
CVE-2026-115382Medium· 4.8Wasmtime wasi:http implementation panics with a zero timeout supplied