# wasi-http p2: outgoing content-length can be invalid or not match body Advisory record · `GHSA-h4wp-g4x3-7398` - **Identifiers:** `GHSA-h4wp-g4x3-7398` · `RUSTSEC-2026-0421` - **State:** Confirmed - **Severity:** CVSS 3.7 Low - **Critical:** No - **Published:** 29 Oct 2026 - **Updated:** 30 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 29 Oct 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `wasmtime-wasi-http` (crates.io): affected `>=0.0.0-0, <36.0.20 || >=37.0.0, <48.0.8 || >=49.0.0, <49.0.5 || >=50.0.0, <50.0.1`; fixed in `36.0.20`, `48.0.8`, `49.0.5`, `50.0.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The wasmtime-wasi-http crate is affected in versions before 36.0.20, from 37.0.0 before 48.0.8, from 49.0.0 before 49.0.5, and from 50.0.0 before 50.0.1. The source gives few details: it describes an issue where the outgoing content-length header can be invalid or not match the body, but does not describe the attacker's requirements or impact. Upgrade to 36.0.20, 48.0.8, 49.0.5, 50.0.1, or a later version in the same line. Written 3 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 3.7 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`, from OSV - **CISA KEV:** Not listed. - **EPSS:** No score. ## Timeline - 31 Oct 2026, 14:24 UTC: First seen by agentprime - 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0421) ## Sources - [GitHub Advisory Database: GHSA-h4wp-g4x3-7398](https://github.com/advisories/GHSA-h4wp-g4x3-7398) - [OSV: GHSA-h4wp-g4x3-7398](https://osv.dev/vulnerability/GHSA-h4wp-g4x3-7398) - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .