CVE-2026-119130

Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 HTTP Request Target Smuggling

Published Oct 29, 2026 CVSS 4.0 · 2.1 Low EPSS < 1% KEV · Not listed
Description
Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 does not verify that set-path-with-query values in wasmtime-wasi-http are paths, so absolute-form URLs are written verbatim as the HTTP/1.1 request target while the connection uses the allowed authority. A malicious guest can supply an absolute URL that a forward proxy or gateway at that authority honors, reaching hosts disallowed by embedder filtering policies.

Analysis

AI-generated

Technical impact

The vulnerability arises when Wasmtime fails to validate that the set-path-with-query values supplied by Wasmtime‑wasi‑http are proper path segments. Because absolute‑form URLs are written verbatim into the HTTP/1.1 request target, an attacker controlling a guest can supply an absolute URL that a forward proxy or gateway honoring that authority will honor. Consequently, the guest can send requests to hosts that the embedder’s filtering policy intends to block, allowing unauthorized outbound network access.

Affected Systems

The issue exists in Wasmtime releases prior to 36.0.18, 37.0.0 prior to 48.0.6, and 49.0.0 prior to 49.0.3. These are the bytecodealliance:wasmtime binaries; the affected versions are the ones listed above.

Risk and Exploitability

The CVSS score of 2.1 indicates a low overall severity, and no EPSS score is available. The vulnerability is exploitable by a guest application running inside a Wasmtime instance. By providing a crafted absolute‑form URL, an attacker can cause a forward proxy or gateway to relay traffic to arbitrary hosts, bypassing the embedder’s host filtering. Because the vulnerability relies on a malicious guest and an existing proxy or gateway that processes absolute URLs, the likelihood of exploitation in the wild is limited. The vulnerability is currently not listed in CISA’s KEV catalogue, further suggesting a low threat level, but any system that relies on strict host filtering should verify that the embedder limits absolute target URLs or upgrade to a fixed release.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Wasmtime to a fixed release (36.0.18 or later, 37.0.0≥48.0.6, or 49.0.0≥49.0.3).
  • Configure the embedder’s host filtering logic to disallow or reject absolute form URLs supplied by guests.
  • Monitor outbound traffic from Wasmtime instances for unexpected host destinations to detect any unauthorized requests.

Generated by OpenCVE AI on October 29, 2026 at 17:31 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 does not verify that set-path-with-query values in wasmtime-wasi-http are paths, so absolute-form URLs are written verbatim as the HTTP/1.1 request target while the connection uses the allowed authority. A malicious guest can supply an absolute URL that a forward proxy or gateway at that authority honors, reaching hosts disallowed by embedder filtering policies.
Title Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 HTTP Request Target Smuggling
First Time appeared Bytecodealliance
Bytecodealliance wasmtime
Weaknesses CWE-20
CPEs cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:*:*:*
Vendors & Products Bytecodealliance
Bytecodealliance wasmtime
References
Metrics cvssV3_1

{'score': 2.6, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 2.1, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-20

    Improper Input Validation

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 29, 2026, 8:14 PM
Reserved
Oct 29, 2026, 2:26 PM
Status
Deferred
Published
Oct 29, 2026, 4:18 PM
Modified
Oct 29, 2026, 9:17 PM