CVE-2026-27204 Wasmtime WASI implementations are vulnerable to guest-controlled resource exhaustion
A malicious WebAssembly guest can exhaust host resources in Wasmtime, causing denial of service; embedders must upgrade and configure limits.
- 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-27204?
CVE-2026-27204 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 WASI host interfaces are susceptible to guest-controlled resource exhaustion on the host. Wasmtime did not appropriately place limits on resource allocations requested by the guests. This serves as a Denial of Service vector. Wasmtime 24.0.6, 36.0.6, 40.0.4, 41.0.4, and 42.0.0 have all been released with the fix for this issue. These versions do not prevent this issue in their default configuration to avoid breaking preexisting behaviors. All versions of Wasmtime have appropriate knobs to prevent this behavior, and Wasmtime 42.0.0-and-later will have these knobs tuned by default to prevent this issue from happening. There are no known workarounds for this issue without upgrading. Embedders are recommended to upgrade and configure their embeddings as necessary to prevent possibly-malicious guests from triggering this issue.
Which versions are affected by CVE-2026-27204?
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-27204?
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-27204 being exploited?
There is no known exploitation of CVE-2026-27204 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-27204, GHSA-852m-cvvp-9p4w, JLSEC-2026-1352, RUSTSEC-2026-0020, UBUNTU-CVE-2026-27204.