Loading...
Skip to main content

CVE-2026-54786 — Wasmtime has a leak in wasmtime-wasi — CVE Details

LOW

Wasmtime has a leak in WASIp1 `fd_renumber` implementation

Published August 26, 2026Updated August 26, 2026Source: osv

Summary

### Impact Wasmtime's native implementation of WASIp1 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. This means that guests can, in a loop, use `fd_renumber` to cause hosts to exhaust resources or exhaust file descriptors. This bug only affects the native implementation of WASIp1. This means 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. ### Patches Wasmtime 24.0.10, 36.0.11, 44.0.3, and 45.0.2 have been released which fix this issue. ### Workarounds There are no workarounds for this issue and hosts are recommended to update.

Advisory Timeline

  • First published August 26, 2026 (47 days ago).
  • Last revised August 26, 2026 — 0 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Cargo
Update wasmtime-wasi to 24.0.10 or later
cargo update -p wasmtime-wasi --precise 24.0.10
Cargo
Update wasmtime-wasi to 44.0.3 or later
cargo update -p wasmtime-wasi --precise 44.0.3
Cargo
Update wasmtime-wasi to 36.0.11 or later
cargo update -p wasmtime-wasi --precise 36.0.11
Cargo
Update wasmtime-wasi to 45.0.2 or later
cargo update -p wasmtime-wasi --precise 45.0.2

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (4)

Affects 1 ecosystem: crates.io (1).

PackageEcosystemAffectedFixed In
wasmtime-wasi
crates.io
All versions24.0.10
wasmtime-wasi
crates.io
All versions44.0.3
wasmtime-wasi
crates.io
All versions36.0.11
wasmtime-wasi
crates.io
All versions45.0.2

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-400
    Uncontrolled Resource ConsumptionMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 5.0 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L

Frequently Asked Questions

What is CVE-2026-54786?
Wasmtime has a leak in WASIp1 `fd_renumber` implementation This vulnerability has been assigned a severity rating of LOW (CVSS score: 5.0/10).
How do I check if my project is affected by CVE-2026-54786?
CVE-2026-54786 affects wasmtime-wasi. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-54786 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
5.0

Exploitation requires specific conditions or has limited impact. Remediate within weeks.

Also Known As

GHSA-3p27-qvp9-27qf
RUSTSEC-2026-0182

Related CVEs

  • CVE-2026-47261
    HIGH

    WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction

  • CVE-2026-47261
    HIGH

    wasmtime-wasi: WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction

  • CVE-2026-58494
    MEDIUM

    WASI hard links and renames bypass wasmtime-wasi's FilePerms for destination

  • CVE-2026-34945
    LOW

    Wasmtime has host data leakage with 64-bit tables and Winch

  • CVE-2026-41677
    LOW

    rust-opennssl has an Out-of-bounds read in PEM password callback when returning an oversized length

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies