CVE-2026-54786

Wasmtime: Leak in WASIp1 `fd_renumber` implementation

MEDIUM
5
CVSS Score
Published: July 1, 2026 at 08:12 PM UTC
Updated: October 25, 2026 at 04:10 PM UTC
1 product affected across 1 vendorWasmtime

Using wasmtime by bytecodealliance?

Get instant alerts when new vulnerabilities affect wasmtime - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 24.0.1025.0.0 ≤ v < 36.0.1137.0.0 ≤ v < 44.0.345.0.0 ≤ v < 45.0.2
Affected range stops below 24.0.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 36.0.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 44.0.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 45.0.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-772CWE-400

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card