Live › vulnerability › CVE-2026-119130
Wasmtime's wasmtime-wasi-http does not check that set-path-with-query values are paths, so absolute-form URLs are sent as the HTTP/1.1 request target. A malicious guest can use this to make a forward proxy or gateway reach hosts the embedder's filtering policy disallows.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 16:25 UTC. All times on this page are UTC.
Applications that embed Wasmtime and run untrusted WebAssembly guests using wasmtime-wasi-http with outbound HTTP, especially where a forward proxy or gateway sits behind the allowed authority. Teams that do not run untrusted guests or do not use wasi-http outbound requests can likely skip it.
No product ranges from the sources yet.
wasmtime --version, and compare it against the affected ranges below.wasmtime before 36.0.18 fixed to 36.0.18wasmtime before fixed to 37.0.048.0.648.0.6wasmtime 49.0.0 before 49.0.3 fixed to 49.0.3Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-119130")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.