Live › vulnerability › CVE-2026-115384
Go to dashboardWasmtime versions 39.0.0 through 48.0.3 and 49.0.0 through 49.0.1 fail to validate async callback result types in the component model. A malicious guest component can write about 16KB onto the native host stack, overwriting return addresses to crash the host or escape the WebAssembly sandbox.
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.
| Product | Ecosystem | Affected | Fixed in |
|---|
| wasmtime | crates.io | >= 39.0.0, < 48.0.4; >= 49.0.0, < 49.0.2 | 48.0.4, 49.0.2 |
Run wasmtime --version and check whether it falls in 39.0.0-48.0.3 or 49.0.0-49.0.1, or check Cargo.lock for wasmtime entries in those ranges.
48.0.4 or 49.0.2 (or any later release)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Wasmtime 39.0.0 before 48.0.4 and 49.0.0 before 49.0.2 contains a stack buffer overflow vulnerability that allows malicious guests to write ~16KB to the native stack via unvalidated async callback result types. Attackers can supply components with mistyped component-model-async callback functions to overwrite return addresses, crashing the host or escaping the sandbox.
This page as .md · .json · in your agent: get_signal("CVE-2026-115384")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.