Is wasmtime-wasi affected by CVE-2025-53901?

crates.io wasmtime-wasi is affected in =25.0.0 =34.0.0 <34.0.2.

Is CVE-2025-53901 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.3%.

low

CVE-2025-53901

Q: Is CVE-2025-53901 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.3%.

crates.io · wasmtime-wasi • crates.io · wasmtime

Summary

Wasmtime CLI is vulnerable to host panic through its fd_renumber function

Severity: low
EPSS: 0.3% (p21)
Also known as: GHSA-fm79-3f68-h2fc, GHSA-fm79-3f68-h2fc#wasmtime, GHSA-fm79-3f68-h2fc#wasmtime-wasi, RUSTSEC-2025-0046
Published: 2025-07-18

References

https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-fm79-3f68-h2fc
https://nvd.nist.gov/vuln/detail/CVE-2025-53901
https://github.com/bytecodealliance/wasmtime/pull/11277

Related advisories

CVE-2026-47261 — high · crates.io/wasmtime-wasi
GHSA-3p27-qvp9-27qf — medium · crates.io/wasmtime-wasi

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.