CVE-2026-115892: Wasmtime: Panic lowering a host-created component model stream into a guest that expects a different payload type

Published Oct 23, 2026
·
Updated

Summary

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.

Impact

This affects embedders that do all of the following:

1. Create streams or futures on the host with StreamReader::new or FutureReader::new 2. Pass them to guest code and receive them back as StreamAny, FutureAny, Val::Stream/Val::Future, or a typed reader whose payload is one of these. 3. Pass them on to a guest function whose 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.

Other sources

Wasmtime is a runtime for WebAssembly. From 46.0.0 until 48.0.7 and 49.0.4, lowering a host-created component-model stream or future into a guest can omit a required payload-type check after the value passes through guest code and returns through StreamAny, FutureAny, Val::Stream, Val::Future, or an equivalent typed reader. A malicious guest that controls exported function types or returned values can cause the host to pass the type-erased value to a guest expecting a different payload type, which panics the Wasmtime host. This issue is fixed in versions 48.0.7 and 49.0.4.

— Ubuntu

Affected Software

7 affected componentsFixes available
Bytecode Alliance Wasmtime>=46.0.0<48.0.7, >=49.0.0<49.0.4
rust/wasmtime>=49.0.0<49.0.4
49.0.4
rust/wasmtime>=46.0.0<48.0.7
48.0.7
ubuntu/rust-wasmtime*
ubuntu/rust-wasmtime*
ubuntu/rust-wasmtime*
debian/rust-wasmtime
26.0.1+dfsg-336.0.13+dfsg-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade rust/wasmtime to a version that resolves this vulnerability.

    Fixed in 49.0.4
  2. Upgrade

    Upgrade rust/wasmtime to a version that resolves this vulnerability.

    Fixed in 48.0.7
  3. Upgrade

    Upgrade debian/rust-wasmtime to a version that resolves this vulnerability.

    Fixed in 26.0.1+dfsg-3Fixed in 36.0.13+dfsg-1
  4. Upgrade

    Upgrade Wasmtime to a version that resolves this vulnerability.

    Fixed in 48.0.7
  5. Upgrade

    Upgrade Wasmtime to a version that resolves this vulnerability.

    Fixed in 49.0.4

Event History

Oct 23, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·09:26 PM
Data Sourced
via MITRE·09:26 PM
DescriptionWeakness
Data Sourced
via OSV·09:26 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·10:04 PM
Data Sourced
via GitHub·10:04 PM
DescriptionWeaknessAffected Software
Data Sourced
via OSV·10:16 PM
Affected Software
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Only embedders that create component-model streams or futures on the host with StreamReader::new or FutureReader::new, pass them to guest code, receive them back through a type-erased or equivalent representation, and then pass them to a guest function with a different payload type are affected.

2

Can guest code trigger the type mismatch?

Yes. A guest can cause the mismatch when it controls the types of exported functions or the values it returns, allowing a stream or future to be passed onward with a payload type different from the one used when the host created it.

3

What return paths should be reviewed during triage?

Review flows where host-created streams or futures return as StreamAny, FutureAny, Val::Stream, Val::Future, or a typed reader whose payload is one of those types. Determine whether any such value can later be supplied to a guest function expecting a different stream or future payload type.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203