Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-r8xh-cgf7-392j

`wasi-http`: Guests can add conflicting content lengths to messages

CVSS 6.3 MediumEPSS 0.0022 · 13th percentile

Published by the GitHub Advisory Database at 19 Oct 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wasmtime-wasi-httpcrates.io>=0.0.0-0, <36.0.19 || >=37.0.0, <48.0.7 || >=49.0.0, <49.0.436.0.19, 48.0.7, 49.0.4
Identifiers
GHSA-r8xh-cgf7-392j · CVE-2026-121441 · RUSTSEC-2026-0376
Weakness (CWE)
CWE-444
Tags
Published
19 Oct 2026
Updated
4 Nov 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The wasmtime-wasi-http crate is vulnerable in versions before 36.0.19, from 37.0.0 before 48.0.7, and from 49.0.0 before 49.0.4. The source gives few details: it is a RustSec entry that points to the GitHub advisory for the full description, and it concerns guests adding conflicting content lengths to messages. Upgrade to 36.0.19, 48.0.7, or 49.0.4 depending on your release 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

ScoreRatingCVSSVectorSource
6.3 Medium 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 13th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV
  3. 3 Nov 2026, 14:38 UTC Confirmed by the CVE List
  4. 3 Nov 2026, 15:25 UTC Confirmed by NVD

Sources

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.