wasmtime
Affected
- introduced
39.0.0, fixed40.0.4(semver)
Fixed versions
40.0.4
Fix
- Fixed version
40.0.4cargo update -p wasmtime --precise 40.0.4
Advisory
Also known as: CVE-2026-27195, RUSTSEC-2026-0022
Wasmtime is vulnerable to panic when dropping a [Typed]Func::call_async future
The affected versions of Wasmtime can panic if the host embedder drops the future returned by wasmtime::component::[Typed]Func::call_async before it resolves.
Details
Starting with Wasmtime 39.0.0, the component-model-async feature became the default, which brought with it a new implementation of [Typed]Func::call_async which made it capable of calling async-typed guest export functions. However, that implementation had a bug leading to a panic under certain circumstances:
[Typed]Func::call_async on a function exported by a component, polling the returned Future once.LinkerInstance::func_wrap_async which yields, or due an epoch interruption.Future after polling it once. This leaves the component instance in a non-reenterable state since the call never had a chance to complete.[Typed]Func::call_async again, polling the returned Future. Since the component instance cannot be entered at this point, the call traps, but not before allocating a task and thread for the call.Future. This panics due to the runtime attempting to dispose of the task created above, which panics since the thread has not yet exited.Impact
When a host embedder using the affected versions of Wasmtime calls wasmtime::component::[Typed]Func::call_async on a guest export and then drops the returned future without waiting for it to resolve, and then does so again with the same component instance, Wasmtime will panic. Embeddings that have the component-model-async compile-time feature disabled are unaffected.
Patches
Wasmtime 40.0.4 and 41.0.4 have been patched to fix this issue. Versions 42.0.0 and later are not affected.
Workarounds
If an embedding is not actually using any component-model-async features then disabling the component-model-async Cargo feature can work around this issue. This issue can also be worked around by either ensuring every call_async future is awaited until it completes or refraining from using the Store again after dropping a not-yet-resolved call_async future.
Resources
This was first reported in https://bytecodealliance.zulipchat.com/#narrow/channel/206238-general/topic/Panic.20in.20Wasmtime.2041.2E0.2E3.20.28runtime.2Fconcurrent.2Fcomponent.29
Medium Basis: The source's own band: MODERATE
39.0.0, fixed 40.0.4 (semver)40.0.4
40.0.4cargo update -p wasmtime --precise 40.0.441.0.0, fixed 41.0.4 (semver)41.0.4
41.0.4cargo update -p wasmtime --precise 41.0.4Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0