Wasmtime: Panic when a component cancels a stream or future copy on the wrong end
Affects wasmtimeSource GCVE Database
CVSS 3.1 Low · fixed in 50.0.2 : update wasmtime when convenient.
Data as of 19 Nov 2026, 09:50 UTC
- Patch
- Available – fixed in 50.0.2, 49.0.6, 48.0.9
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:LWhat to do
Upgrade wasmtime to 50.0.2, 49.0.6 or 48.0.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iowasmtimepkg:cargo/wasmtimeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to Wasmtime versions 48.0.9, 49.0.6, or 50.0.2 or later to remediate this issue. A patch is available and should be applied to prevent potential denial of service caused by this panic condition.
Description
Wasmtime versions from 46.0.0 up to but not including 48.0.9, from 49.0.0 up to but not including 49.0.6, and from 50.0.0 up to but not including 50.0.2 contain a vulnerability where a panic occurs if a component cancels a stream or future copy on the wrong end. This issue has a low severity score and does not impact confidentiality or integrity but can cause availability disruption. Fixed versions are 48.0.9, 49.0.6, and 50.0.2.