wasmtime
Affected
- introduced
0, fixed24.0.6(semver)
Fixed versions
24.0.6
Fix
- Fixed version
24.0.6cargo update -p wasmtime --precise 24.0.6
Advisory
Also known as: CVE-2026-27572, RUSTSEC-2026-0021
Wasmtime can panic when adding excessive fields to a wasi:http/types.fields instance
Impact
Wasmtime's implementation of the wasi:http/types.fields resource is susceptible to panics when too many fields are added to the set of headers. Wasmtime's implementation in the wasmtime-wasi-http crate is backed by a data structure which panics when it reaches excessive capacity and this condition was not handled gracefully in Wasmtime. Panicking in a WASI implementation is a Denial of Service vector for embedders and is treated as a security vulnerability in Wasmtime.
Patches
Wasmtime 24.0.6, 36.0.6, 40.0.4, 41.0.4, and 42.0.0 patch this vulnerability and return a trap to the guest instead of panicking.
Workarounds
There are no known workarounds at this time, embedders are encouraged to update to a patched version of Wasmtime.
Resources
Medium Basis: The source's own band: MODERATE
0, fixed 24.0.6 (semver)24.0.6
24.0.6cargo update -p wasmtime --precise 24.0.625.0.0, fixed 36.0.6 (semver)36.0.6
36.0.6cargo update -p wasmtime --precise 36.0.637.0.0, fixed 40.0.4 (semver)40.0.4
40.0.4cargo update -p wasmtime --precise 40.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