Live › vulnerability › CVE-2026-115391
Go to dashboardWasmtime's WASIp3 implementation copies and buffers every byte of guest-specified-length writes on the host with no limit. A malicious guest module can offer large buffers to file or HTTP write streams and exhaust the host's memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only hosts that run untrusted WebAssembly guests through Wasmtime's WASIp3 interface, with file or HTTP write streams, are exposed. Teams running only their own trusted guest code, or versions outside 46.0.0-46.0.2 and 47.0.0-47.0.3, can skip it.
No product ranges from the sources yet.
wasmtime --version and compare against 46.0.3 and 47.0.4wasmtime crate or library version in projects that embed it46.0.3 (46.x line) or 47.0.4 (47.x line)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Wasmtime 46.0.0 before 46.0.3 and 47.0.0 before 47.0.4 contains an uncontrolled resource allocation vulnerability in its WASIp3 implementation that buffers guest-specified-length writes on the host without limit. Malicious guests can offer large buffers to WASIp3 file or HTTP write streams, causing the host to copy and buffer all bytes, bounded only by guest linear memory, exhausting host memory.
This page as .md · .json · in your agent: get_signal("CVE-2026-115391")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.