CVE-2025-53901: RUSTSEC-2025-0046 - Host panic with `fd_renumber` WASIp1 function

CVE-2025-53901 · Severity: low · CVSS 3.1 · Published 2025-07-18

Host panic with `fd_renumber` WASIp1 function

Technologies: wasmtime (crates.io), wasmtime-wasi (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2025-53901 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-53901 being exploited in the wild.
How severe is CVE-2025-53901?
Low severity, with a CVSS score of 3.1, published 18 July 2025.
Which products and versions are affected?
wasmtime (crates.io) SEMVER:introduced=10.0.0,fixed=24.0.4, SEMVER:introduced=10.0.0,fixed=24.0.4,introduced=25.0.0,fixed=33.0.2,introduced=34.0.0,fixed=34.0.2; wasmtime-wasi (crates.io) SEMVER:introduced=0,fixed=24.0.4.
Is there a fix for CVE-2025-53901?
Yes. wasmtime (crates.io): upgrade to 24.0.4, 34.0.2 or later; wasmtime-wasi (crates.io): upgrade to 24.0.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-53901?
Check whether you run wasmtime (crates.io) or wasmtime-wasi (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • wasmtime (crates.io): upgrade to 24.0.4, 34.0.2 or later
    cargo update -p wasmtime
  • wasmtime-wasi (crates.io): upgrade to 24.0.4 or later
    cargo update -p wasmtime-wasi

Affected products

  • wasmtime (crates.io) SEMVER:introduced=10.0.0,fixed=24.0.4, SEMVER:introduced=10.0.0,fixed=24.0.4,introduced=25.0.0,fixed=33.0.2,introduced=34.0.0,fixed=34.0.2
  • wasmtime-wasi (crates.io) SEMVER:introduced=0,fixed=24.0.4

Identifiers

  • CVE-2025-53901
  • GHSA-fm79-3f68-h2fc
  • RUSTSEC-2025-0046

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.