Live › vulnerability › CVE-2026-115892
Go to dashboardA host application using Wasmtime can panic when it passes a component model stream or future it created to a guest with a different payload type than the one the host used. A malicious guest can trigger the mismatch, causing a denial of service in the host process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 22:05 UTC, 0h before NVD. All times on this page are UTC.
Only embedders that create streams or futures on the host, send them to guest code, receive them back under a type-erased type, and pass them to a guest function with a different payload type are exposed. Hosts that use only statically typed readers with concrete payload types throughout, or that never round-trip their own streams or futures through a guest, are not affected.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| wasmtime | cargo | >= 46.0.0, < 48.0.7 | 48.0.7 |
| wasmtime | cargo | >= 49.0.0, < 49.0.4 | 49.0.4 |
StreamReader::new or FutureReader::new in host code, then check whether those streams or futures are passed through guest code and returned as StreamAny, FutureAny, Val::Stream or Val::Future.cargo tree -i wasmtime; affected are >= 46.0.0, < 48.0.7 and >= 49.0.0, < 49.0.4.wasmtime crate to 48.0.7 on the 48.x line, or to 49.0.4 on the 49.x line.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Wasmtime may panic when the host lowers a component model stream or future into a guest, if the host created that stream or future with one payload type and the guest expects a different one. This can happen when an embedder creates a stream or future, passes it through a guest, receives it back under a type-erased type such as StreamAny or FutureAny, and then passes it to a guest function with a different payload type.
GHSA-63h4-6cx9-pjfj is a related advisory also fixing issues within this area, and this advisory is being issued for portions of Wasmtime that were not fixed as part of that advisory.
This affects embedders that do all of the following:
StreamReader::new or FutureReader::newStreamAny, FutureAny, Val::Stream/Val::Future, or a typed reader whose payload is one of these.stream or future payload type differs from the type the host created them with.A guest can cause the mismatch in step 3 when it controls the types of the functions it exports or of the values it returns. In that case a malicious guest can make the host panic, a denial of service. Embedders that only use statically typed StreamReader<T>/FutureReader<T> with concrete payload types throughout, or that never pass streams or futures they created through a guest and back, are not affected.
This page as .md · .json · in your agent: get_signal("CVE-2026-115892")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.