CVE-2026-54786 Wasmtime: Leak in WASIp1 `fd_renumber` implementation
A malicious WebAssembly guest can exhaust host file descriptors via fd_renumber, causing denial of service in Wasmtime runtimes exposing file access.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54786?
CVE-2026-54786 is a low-severity denial of service vulnerability in bytecodealliance wasmtime, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Wasmtime is a runtime for WebAssembly. All versions prior to 24.0.10; versions 25.0.0 through those before 36.0.11; versions 37.0.0 through those before 44.0.3; and versions 45.0.0 and 45.0.1 contain a native implementation of WASIp1 which suffers from a leak in the fd_renumber function where the file descriptor being renumbered to is not properly closed. Wasmtime's implementation erroneously only updated the table of descriptors for WASIp1 and didn't update the underlying table of descriptors used by the host. This behavior means that while fd_renumber works correctly from a guest's perspective it ends up leaking resources in the host that aren't cleaned up until the corresponding Store is destroyed. In a loop, guests can use fd_renumber to cause hosts to exhaust both resources and file descriptors. This bug only affects the native implementation of WASIp1, meaning that only runtimes which load core wasm modules and expose fd_renumber are affected. Runtimes are additionally only affected if they expose the ability to acquire a file descriptor, such as opening a file. For runtimes that deny access to files they are unaffected. This issue has been fixed in versions 24.0.10, 36.0.11, 44.0.3, and 45.0.2.
Which versions are affected by CVE-2026-54786?
9 open source packages ship an affected version, including wasmtime-wasi. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
wasmtime-wasi crates.io | All versions | 24.0.10 |
wasmtime-wasi crates.io | All versions | 24.0.10 |
wasmtime-wasi crates.io | From 0.0.0-0 | 24.0.10, 36.0.11, 44.0.3, 45.0.2 |
wasmtime-wasi crates.io | From 25.0.0 | 36.0.11 |
wasmtime-wasi crates.io | From 25.0.0 | 36.0.11 |
wasmtime-wasi crates.io | From 37.0.0 | 44.0.3 |
3 more packages
wasmtime-wasi crates.io | From 37.0.0 | 44.0.3 |
wasmtime-wasi crates.io | From 45.0.0 | 45.0.2 |
wasmtime-wasi crates.io | From 45.0.0 | 45.0.2 |
Products include Bytecodealliance Wasmtime.
How do I fix CVE-2026-54786?
Upgrade wasmtime-wasi to a fixed version for your release line: 24.0.10, 36.0.11, 44.0.3 or 45.0.2.
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-54786 being exploited?
There is no known exploitation of CVE-2026-54786 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-54786, GHSA-3p27-qvp9-27qf, JLSEC-2026-1367, MINI-cx8g-cc87-9wcv, MINI-q5m8-f2cv-pr3j, MINI-w46j-9jc9-7p3m and 2 more.