p PatchFirst

CVE-2026-27572

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

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 6.9 · Medium · EPSS 0.7% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • wasmtime

    Versions
    • < 24.0.6: Affected
    • >= 25.0.0, < 36.0.6: Affected
    • >= 37.0.0, < 40.0.4: Affected
    • >= 41.0.0, < 41.0.4: Affected

    No fix published

  • rust-wasmtime Debian:13

    Versions
    • 26.0.1+dfsg-10
    • 26.0.1+dfsg-3
    • 26.0.1+dfsg-4
    • 26.0.1+dfsg-5
    • 26.0.1+dfsg-6
    • 26.0.1+dfsg-7
    • 26.0.1+dfsg-8
    • 26.0.1+dfsg-9
    • 27.0.0+dfsg-2
    • 27.0.0+dfsg-3
    • 27.0.0+dfsg-4
    • 28.0.1+dfsg-1
    • 28.0.1+dfsg-2
    • 28.0.1+dfsg-3
    • 29.0.1+dfsg-1
    • 29.0.1+dfsg-2
    • 29.0.1+dfsg-3
    • 29.0.1+dfsg-4
    • 29.0.1+dfsg-5
    • 29.0.1+dfsg-6
    • 29.0.1+dfsg-7
    • 29.0.1+dfsg-8
    • 36.0.11+dfsg-1
    • 36.0.12+dfsg-1
    • 36.0.12+dfsg-2
    • 36.0.12+dfsg-3
    • 36.0.13+dfsg-1
    • 36.0.5+dfsg-1
    • 36.0.5+dfsg-2
    • 36.0.5+dfsg-3
    • 36.0.5+dfsg-4
    • 36.0.5+dfsg-5
    • 36.0.6+dfsg-1
    • 36.0.6+dfsg-2
    • 36.0.6+dfsg-3
    • 36.0.6+dfsg-4
    • 36.0.6+dfsg-5
    • 36.0.6+dfsg-6
    • 36.0.6+dfsg-7
    • 36.0.7+dfsg-1
    • 36.0.8+dfsg-1
    • 36.0.9+dfsg-1
    • 36.0.9+dfsg-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • rust-wasmtime Debian:14

    Versions
    • 26.0.1+dfsg-10
    • 26.0.1+dfsg-3
    • 26.0.1+dfsg-4
    • 26.0.1+dfsg-5
    • 26.0.1+dfsg-6
    • 26.0.1+dfsg-7
    • 26.0.1+dfsg-8
    • 26.0.1+dfsg-9
    • 27.0.0+dfsg-2
    • 27.0.0+dfsg-3
    • 27.0.0+dfsg-4
    • 28.0.1+dfsg-1
    • 28.0.1+dfsg-2
    • 28.0.1+dfsg-3
    • 29.0.1+dfsg-1
    • 29.0.1+dfsg-2
    • 29.0.1+dfsg-3
    • 29.0.1+dfsg-4
    • 29.0.1+dfsg-5
    • 29.0.1+dfsg-6
    • 29.0.1+dfsg-7
    • 29.0.1+dfsg-8
    • 36.0.5+dfsg-1
    • 36.0.5+dfsg-2
    • 36.0.5+dfsg-3
    • 36.0.5+dfsg-4
    • 36.0.5+dfsg-5
    Affected ranges
    • ECOSYSTEM: < 36.0.6+dfsg-1

    Update to 36.0.6+dfsg-1

  • rust-wasmtime Ubuntu:24.04:LTS

    Versions
    • 10.0.1+dfsg-7
    • 15.0.1+dfsg-4
    • 16.0.0+dfsg-2
    • 16.0.0+dfsg-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • rust-wasmtime Ubuntu:25.10

    Versions
    • 26.0.1+dfsg-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • rust-wasmtime Ubuntu:26.10

    Versions
    • 36.0.5+dfsg-1
    • 36.0.13+dfsg-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • rust-wasmtime Ubuntu:26.04:LTS

    Versions
    • 26.0.1+dfsg-3
    • 26.0.1+dfsg-4
    • 28.0.1+dfsg-3
    • 29.0.1+dfsg-5
    • 36.0.5+dfsg-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →