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.