Quick answers
- Is CVE-2026-119141 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119141 being exploited in the wild.
- How severe is CVE-2026-119141?
- Medium severity, with a CVSS score of 5.3, published 29 October 2026.
- Which products and versions are affected?
- Bytecode Alliance Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3.
- Is there a fix for CVE-2026-119141?
- Yes: fixed in 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-119141 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119141?
- 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: 48.0.6, 49.0.3
Technical details
The vulnerability stems from the may_leave flag not being cleared during realloc when lowering stream or future results, allowing guest Wasm code to call back into the host in an invalid state. A malicious module can trigger a host panic by cancelling an active read or re-waiting a waitable-set during realloc. This affects Wasmtime 46.0.0–48.0.5, 49.0.0–49.0.2, and requires network access for exploitation if the host exposes Wasmtime over the network; exploitation requires ability to execute guest WebAssembly code.
Affected products
- Bytecode Alliance Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3
Timeline
- 2026-10-14: advisory: GitHub security advisory published
- 2026-10-29: other: NVD entry published