CVE-2026-27572
Published: 24 February 2026
Summary
CVE-2026-27572 is a high-severity Allocation of Resources Without Limits or Throttling (CWE-770) vulnerability in Bytecodealliance Wasmtime. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 9.5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Threat & Defense at a Glance
Threat & Defense Details
Likely Mitigating ControlsAI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
This control implements explicit throttling on session allocation, addressing the weakness of allocating resources without limits.
Plan testing exercises resource allocation limits and throttling during simulated failures, directly addressing weaknesses that allow unbounded resource use.
Contingency plan updates ensure recovery strategies address unbounded resource allocation, making it harder for attackers to exploit lack of throttling to cause prolonged outages.
Provides continuity when unbounded resource allocation at the primary site leads to exhaustion and downtime.
Alternate services allow operations to continue when primary allocation of resources lacks limits or throttling.
Explicit planning of security-related actions requires defining limits, windows, and resource allocations, making allocation without throttling far less likely.
Measures of performance include tracking allocation behavior and throttling effectiveness, reducing the window for resource exhaustion attacks.
Imposes an inactivity-based limit on network resource allocation, throttling the number of concurrently held connections.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
CVE directly enables T1499.004 via remote exploitation of the Wasmtime WASI HTTP types implementation (excessive header fields causing host panic) to achieve application/system DoS.
NVD 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…
more
`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.
Deeper analysisAI
CVE-2026-27572 affects Wasmtime, a runtime for WebAssembly, specifically its implementation of the `wasi:http/types.fields` resource in the `wasmtime-wasi-http` crate. Prior to versions 24.0.6, 36.0.6, 40.0.4, 41.0.4, and 42.0.0, the component is susceptible to panics when too many fields are added to the set of headers. This stems from an underlying data structure that panics upon reaching excessive capacity, without graceful handling in Wasmtime. Such panics in a WASI implementation are considered a security vulnerability due to their potential impact on embedders.
The vulnerability can be exploited remotely by unauthenticated attackers (AV:N/AC:L/PR:N) who can execute WebAssembly guest code interacting with the affected WASI HTTP types. By adding an excessive number of header fields, attackers trigger a panic, resulting in a denial-of-service (DoS) condition for the embedder hosting the Wasmtime runtime. The CVSS v3.1 base score of 7.5 reflects high availability impact (A:H) with no confidentiality or integrity effects (C:N/I:N).
Patched versions of Wasmtime (24.0.6, 36.0.6, 40.0.4, 41.0.4, and 42.0.0) address the issue by returning a trap to the guest instead of panicking. There are no known workarounds, and embedders are advised to update to a patched release. Related documentation highlights limitations in the underlying http crate's header handling, with fixes detailed in the patching commit and release notes.
Details
- CWE(s)