cve.bz

CVE-2026-126406 Wasmtime before 36.0.20 HTTP Request Smuggling via wasi-http p2 Content-Length

6.3 mediumEPSS 0.3%

Medium (6.3) in bytecodealliance wasmtime. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
The wasmtime-wasi-http p2 implementation in Wasmtime before 36.0.20, 37.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 can send conflicting content-length headers, or ones not matching the body, in outgoing requests. A guest that reuses a received response's headers resource to send a bodyless request can enable request smuggling against non-compliant servers, potentially bypassing embedder destination access controls.

Severity

CVSS 4.0

6.3 medium
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

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-444 Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126406 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126406?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126406?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126406 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126406

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126406](https://cve.bz/cve/badge/CVE-2026-126406.svg)](https://cve.bz/cve/CVE-2026-126406)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126406"><img src="https://cve.bz/cve/badge/CVE-2026-126406.svg" alt="CVE-2026-126406"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bytecodealliance wasmtimebefore 36.0.20
bytecodealliance wasmtimefrom 37.0.0 before 48.0.8
bytecodealliance wasmtimefrom 49.0.0 before 49.0.5
bytecodealliance wasmtimefrom 50.0.0 before 50.0.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu24.04:LTS, 26.04:LTS, 26.10rust-wasmtimeno fix listedUBUNTU-CVE-2026-126406

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-33 HTTP Request Smuggling Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON