CVE-2026-27572 Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance
Attackers can cause a Denial of Service in Wasmtime by adding excessive fields to HTTP headers, triggering a panic in the runtime.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-27572?
CVE-2026-27572 is a medium-severity denial of service vulnerability in bytecodealliance wasmtime, published on 24 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-770
Which versions are affected by CVE-2026-27572?
7 open source packages ship an affected version, including wasmtime. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
wasmtime crates.io | All versions | 24.0.6 |
wasmtime crates.io | All versions | 24.0.6 |
wasmtime crates.io | From 0.0.0-0 | 24.0.6, 36.0.6, 40.0.4, 41.0.4 |
wasmtime crates.io | From 25.0.0 | 36.0.6 |
wasmtime crates.io | From 25.0.0 | 36.0.6 |
wasmtime crates.io | From 37.0.0 | 40.0.4 |
1 more packages
wasmtime crates.io | From 37.0.0 | 40.0.4 |
Products include Bytecodealliance Wasmtime.
How do I fix CVE-2026-27572?
Upgrade wasmtime to a fixed version for your release line: 24.0.6, 36.0.6, 40.0.4 or 41.0.4.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-27572 being exploited?
There is no known exploitation of CVE-2026-27572 in the wild and no public exploit code.
Other vulnerabilities in bytecodealliance wasmtime
- CVE-2026-34971 Wasmtime miscompiled guest heap access enables sandbox escape on aarch64 Cranelift
- CVE-2026-34987 Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access
- CVE-2022-39393 Wasmtime vulnerable to data leakage between instances in the pooling allocator
- CVE-2022-24791 Use after free in Wasmtime
- CVE-2026-47261 Wasmtime: WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction
Sources
Also known as DEBIAN-CVE-2026-27572, GHSA-243v-98vx-264h, JLSEC-2026-1353, RUSTSEC-2026-0021, UBUNTU-CVE-2026-27572.