CVE-2025-53901

LOWNVD 3.53.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 3.5 from GitHub Security Advisory (severity: LOW) published 2025-07-18. NVD baseline CVSS 3.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-21918 (ENISA EUVD) · GHSA-fm79-3f68-h2fc (GitHub Security Advisories)Source: ENISA EUVD

3.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
3.5
EG Score
3.5LOWmedium confidence
EG Risk
16
EG Risk 16/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity35% × 45%
Impact severity (EG Severity): CVSS 3.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (3.5): severity, escalated by confirmed exploitation. This CVE's 3.5 is its impact severity (EG Severity), not escalated.

EG Severity
3.5 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 18, 2025

Last Modified

September 4, 2025

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustwasmtime @ 24.0.4 (fixes >= 10.0.0, < 24.0.4)—ghsa
rustwasmtime @ 33.0.2 (fixes >= 33.0.0, < 33.0.2)—ghsa
rustwasmtime @ 34.0.2 (fixes >= 34.0.0, < 34.0.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
crates.io(2)
PackageVulnerable rangeFix by version rangeDependents
wasmtime—
  • 10.0.0 up to 24.0.4: fixed in 24.0.4
  • 33.0.0 up to 33.0.2: fixed in 33.0.2
  • 34.0.0 up to 34.0.2: fixed in 34.0.2
  • 25.0.0 up to 33.0.2: fixed in 33.0.2
—
wasmtime-wasi—
  • every version up to 24.0.4: fixed in 24.0.4
  • 25.0.0 up to 33.0.2: fixed in 33.0.2
  • 34.0.0 up to 34.0.2: fixed in 34.0.2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-wasmtime26.0.1+dfsg-10 ... 36.0.9+dfsg-2 (43 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-wasmtime26.0.1+dfsg-10 ... 29.0.1+dfsg-8 (22 versions)
  • every version up to 36.0.5+dfsg-1: fixed in 36.0.5+dfsg-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-11-01 08:04 UTCGHSA enrichmentGHSA-fm79-3f68-h2fc · GitHub severity LOW · GitHub CVSS 3.5
  4. 2026-11-01 08:04 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-25 16:19 UTCEG score recompute
  13. 2026-10-25 10:38 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-18 05:26 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 70 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-12 16:57 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-11 20:31 UTCEG score recompute
  5. 2026-10-11 18:42 UTCEG score recompute
  6. 2026-10-11 15:18 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-10-02 08:41 UTCOSV refresh
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-09-26 00:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  24. 2026-09-21 21:06 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  25. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  26. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  27. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  28. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  29. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  30. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  31. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  32. 2026-09-13 06:35 UTCOSV refresh
  33. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  34. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  36. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  37. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  39. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  40. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  41. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  42. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  43. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  44. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  45. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  46. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  47. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  48. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  49. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  50. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-08-25 07:26 UTCOSV refresh
  52. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  53. 2026-08-24 09:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  54. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  55. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  56. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  57. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  59. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  61. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  62. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  63. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  64. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  65. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  66. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  67. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  68. 2026-08-09 01:19 UTCOSV refresh
  69. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  70. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.3% · 22nd percentile

Frequently asked(5)

What is CVE-2025-53901?
CVE-2025-53901 is a low-severity vulnerability; its CVE record was published on 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…
When was the CVE record for CVE-2025-53901 published?
The CVE record for CVE-2025-53901 was published on July 18, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 4, 2025; the record at its source may have been updated since.
Is CVE-2025-53901 actively exploited?
CVE-2025-53901 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-53901?
CVE-2025-53901 has a CVSS v3 base score of 3.5 (NVD).
How do I remediate CVE-2025-53901?
A fix for CVE-2025-53901 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-53901

Explore →

Is Your Infrastructure Affected by CVE-2025-53901?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.