Advisory

GHSA-243v-98vx-264h

Also known as: CVE-2026-27572, RUSTSEC-2026-0021

Summary

Wasmtime can panic when adding excessive fields to a wasi:http/types.fields instance

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-02-24 21:08 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

wasmtime

crates.io · All systems

Affected

  • introduced 0, fixed 24.0.6 (semver)

Fixed versions

24.0.6

Fix

  • Fixed version 24.0.6
    cargo update -p wasmtime --precise 24.0.6

wasmtime

crates.io · All systems

Affected

  • introduced 25.0.0, fixed 36.0.6 (semver)

Fixed versions

36.0.6

Fix

  • Fixed version 36.0.6
    cargo update -p wasmtime --precise 36.0.6

wasmtime

crates.io · All systems

Affected

  • introduced 37.0.0, fixed 40.0.4 (semver)

Fixed versions

40.0.4

Fix

  • Fixed version 40.0.4
    cargo update -p wasmtime --precise 40.0.4

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences