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

Published Feb 24, 2026
·
Updated

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

Limitations of http::HeaderMap

Other sources

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.

NVD

Affected Software

8 affected componentsFixes available
rust/wasmtime>=41.0.0<41.0.4
41.0.4
rust/wasmtime>=37.0.0<40.0.4
40.0.4
rust/wasmtime>=25.0.0<36.0.6
36.0.6
rust/wasmtime<24.0.6
24.0.6
bytecodealliance Wasmtime Rust<24.0.6
bytecodealliance Wasmtime Rust>=25.0.0<36.0.6
bytecodealliance Wasmtime Rust>=37.0.0<40.0.4
bytecodealliance Wasmtime Rust>=41.0.0<41.0.4

Event History

Feb 24, 2026
Advisory Published
via GitHub·09:08 PM
Data Sourced
via GitHub·09:08 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·09:31 PM
Data Sourced
via MITRE·09:31 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-27572?

CVE-2026-27572 has been classified as a medium severity vulnerability due to its potential to cause application panics.

2

How do I fix CVE-2026-27572?

To fix CVE-2026-27572, update your Wasmtime installation to version 41.0.4, 40.0.4, 36.0.6, or 24.0.6 depending on your current version.

3

What causes CVE-2026-27572 to occur?

CVE-2026-27572 occurs when excessive fields are added to a `wasi:http/types.fields` instance in Wasmtime.

4

Which versions of Wasmtime are affected by CVE-2026-27572?

Versions of Wasmtime affected by CVE-2026-27572 include 41.0.0 to 41.0.4, 40.0.0 to 40.0.4, 37.0.0 to 36.0.6, and below 24.0.6.

5

What is the impact of CVE-2026-27572?

The impact of CVE-2026-27572 is that it can lead to application crashes or panics when handling HTTP headers.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203