Mend.io Vulnerability Database
The largest open source vulnerability database
What is a Vulnerability ID?
New vulnerability? Tell us about it!
CVE-2025-53901
July 18, 2025
Wasmtime is a runtime for WebAssembly. Prior to versions 24.0.4, 33.0.2, and 34.0.2, a bug in Wasmtime's implementation of the WASIp1 set of import functions can lead to a WebAssembly guest inducing a panic in the host (embedder). The specific bug is triggered by calling "path_open" after calling "fd_renumber" with either two equal argument values or a second argument being equal to a previously-closed file descriptor number value. The corrupt state introduced in "fd_renumber" will lead to the subsequent opening of a file descriptor to panic. This panic cannot introduce memory unsafety or allow WebAssembly to break outside of its sandbox, however. There is no possible heap corruption or memory unsafety from this panic. This bug is in the implementation of Wasmtime's "wasmtime-wasi" crate which provides an implementation of WASIp1. The bug requires a specially crafted call to "fd_renumber" in addition to the ability to open a subsequent file descriptor. Opening a second file descriptor is only possible when a preopened directory was provided to the guest, and this is common amongst embeddings. A panic in the host is considered a denial-of-service vector for WebAssembly embedders and is thus a security issue in Wasmtime. This bug does not affect WASIp2 and embedders using components. In accordance with Wasmtime's release process, patch releases are available as 24.0.4, 33.0.2, and 34.0.2. Users of other release of Wasmtime are recommended to move to a supported release of Wasmtime. Embedders who are using components or are not providing guest access to create more file descriptors (e.g. via a preopened filesystem directory) are not affected by this issue. Otherwise, there is no workaround at this time, and affected embeddings are recommended to update to a patched version which will not cause a panic in the host.
Affected Packages
https://github.com/bytecodealliance/wasmtime.git (GITHUB):
Affected version(s) >=v25.0.0 <v33.0.2
Fix Suggestion:
Update to version v33.0.2
https://github.com/bytecodealliance/wasmtime.git (GITHUB):
Affected version(s) >=v0.2.0 <v24.0.4
Fix Suggestion:
Update to version v24.0.4
https://github.com/bytecodealliance/wasmtime.git (GITHUB):
Affected version(s) >=v34.0.0 <v34.0.2
Fix Suggestion:
Update to version v34.0.2
wasmtime-wasi (RUST):
Affected version(s) >=0.2.0 <24.0.4
Fix Suggestion:
Update to version 24.0.4
wasmtime-wasi (RUST):
Affected version(s) >=25.0.0 <33.0.2
Fix Suggestion:
Update to version 33.0.2
wasmtime-wasi (RUST):
Affected version(s) >=34.0.0 <34.0.2
Fix Suggestion:
Update to version 34.0.2
Additional Notes
The description of this vulnerability differs from MITRE.
Do you need more information?
Contact Us
CVSS v4
Base Score:
5.1
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
PASSIVE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
NONE
Vulnerable System Availability
LOW
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
3.5
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Weakness Type (CWE)
Operation on a Resource after Expiration or Release
EPSS
Base Score:
0.10