Skip to content
Fencer Intel
low 3.5

CVE-2025-53901 json

Wasmtime has host panic with `fd_renumber` WASIp1 function

published last yr. modified 28d ago also EUVD-2025-21918 , GHSA-fm79-3f68-h2fc , JLSEC-2026-1349 , RUSTSEC-2025-0046

cvss
3.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io wasmtime-wasi 24.0.4, 33.0.2, 34.0.2
  • crates.io wasmtime 24.0.4, 33.0.2, 34.0.2
  • julia Wasmtime_jll 39.0.0+0
  • bytecodealliance wasmtime 24.0.4, 33.0.2, 34.0.2
  • rust-wasmtime Debian 14 36.0.5+dfsg-1

debian advisories DEBIAN-CVE-2025-53901

  • zellij openSUSE Tumbleweed 0.43.1-2.1
  • kwctl openSUSE Tumbleweed 1.27.1-1.1

opensuse advisories openSUSE-SU-2025:15704-1openSUSE-SU-2025:15398-1

Is CVE-2025-53901 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-53901 updated cvss 3.5

wasmtime: Wasmtime has host panic

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
GitHub 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
OSV 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
OSV 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
crates.io wasmtime-wasi
<24.0.4
>=25.0.0, <33.0.2
>=34.0.0, <34.0.2
24.0.4
33.0.2
34.0.2
crates.io wasmtime
>=10.0.0, <24.0.4
>=33.0.0, <33.0.2
>=34.0.0, <34.0.2
>=25.0.0, <33.0.2
24.0.4
33.0.2
34.0.2
julia Wasmtime_jll
<39.0.0+0
39.0.0+0

Affected products

  • bytecodealliance wasmtime

Classification

Weakness
  • CWE-672 Operation on a Resource after Expiration or Release

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.