Quick answers
- Is CVE-2026-119142 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119142 being exploited in the wild.
- How severe is CVE-2026-119142?
- Medium severity, with a CVSS score of 4.8, published 29 October 2026.
- Which products and versions are affected?
- Bytecode Alliance Wasmtime 46.0.0 before 48.0.6; 49.0.0 before 49.0.3.
- Is there a fix for CVE-2026-119142?
- Yes: fixed in Wasmtime 48.0.6, 49.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119142 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119142?
- Check whether you run Bytecode Alliance Wasmtime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Wasmtime 48.0.6, 49.0.3
Technical details
The vulnerability exists in the Drop implementation for Futures returned by TypedFunc::call_async. When a guest task has not yet started and the Future is dropped, the cleanup code searches only one of several possible locations for work items, returning an error that is unwrapped and escalated to a panic. The attack requires the ability to issue call_async requests that get cancelled before the guest task begins execution.
Affected products
- Bytecode Alliance Wasmtime 46.0.0 before 48.0.6; 49.0.0 before 49.0.3
Timeline
- 2026-10-14: disclosed
- 2026-10-29: advisory