bytecodealliance wasmtime up to 24.0.3/33.0.1/34.0.1 WASIp1 path_open operation after expiration

Summaryinfo

A vulnerability labeled as problematic has been found in bytecodealliance wasmtime up to 24.0.3/33.0.1/34.0.1. This issue affects the function path_open of the component WASIp1 Handler. The manipulation results in operation after expiration. This vulnerability is cataloged as CVE-2025-53901. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in bytecodealliance wasmtime up to 24.0.3/33.0.1/34.0.1. It has been classified as problematic. Affected is the function path_open of the component WASIp1 Handler. The manipulation with an unknown input leads to a operation after expiration vulnerability. CWE is classifying the issue as CWE-672. The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. This is going to have an impact on availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is traded as CVE-2025-53901 since 07/11/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.

Upgrading to version 24.0.4, 33.0.2 or 34.0.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21918). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• bytecodealliance

Name

• wasmtime

Version

• 24.0.0
• 24.0.1
• 24.0.2
• 24.0.3
• 33.0.0
• 33.0.1
• 34.0.0
• 34.0.1

Website

• Product: https://github.com/bytecodealliance/wasmtime/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion