Quick answers
- Is CVE-2026-119132 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119132 being exploited in the wild.
- How severe is CVE-2026-119132?
- Medium severity, with a CVSS score of 4.8, published 29 October 2026.
- Which products and versions are affected?
- Bytecode Alliance Wasmtime 49.0.0 through 49.0.2.
- Is there a fix for CVE-2026-119132?
- Yes: fixed in 49.0.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119132 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119132?
- 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: 49.0.3
Technical details
The vulnerability exists in Wasmtime's fused adapter implementation, where overlapping string transcoding during same-instance component-to-component calls causes a panic instead of raising a trap. Specifically, when a string's source and destination memory locations alias each other, the refactored code path in version 49.0.0+ fails to properly detect and handle this condition, allowing a guest to reach an unsafe code path that panics the host process. This is a network-reachable denial-of-service vector requiring low privileges and passive user interaction (code execution).
Affected products
- Bytecode Alliance Wasmtime 49.0.0 through 49.0.2
Timeline
- 2026-10-14: disclosed
- 2026-10-29: advisory
- 2026-10-29: patched: Wasmtime 49.0.3 released