CVE-2025-25202

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-4088 (ENISA EUVD) · GHSA-qrm9-f75w-hg4c (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Ash Authentication is an authentication framework for Elixir applications. Applications which have been bootstrapped by the igniter installer present since AshAuthentication v4.1.0 and who have used the magic link strategy _or_ are manually revoking tokens are affected by revoked tokens being allowed to verify as valid. Unless one hase implemented any kind of custom token revocation feature in your application, then one will not be affected. The impact here for users using builtin functionality is that magic link tokens are reusable until they expire. With that said, magic link tokens are only valid for 10 minutes, so the surface area for abuse is extremely low here. The flaw is patched in version 4.4.9. Additionally a compile time warning is shown to users with remediation instructions if they upgrade. 4.4.9 ships with an upgrader, so those who use mix igniter.upgrade ash_authentication will have the necessary patch applied. Otherwise, one may run the upgrader manually as described in the error message. As a workaround, delete the generated :revoked? generic action in the token resource. This will cause it to use the one internal to Ash Authentication which has always been correct. Alternatively, manually make the changes that are included in the patch.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.3%
EPSS %ILE
24th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% 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 low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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

February 11, 2025

Last Modified

August 27, 2025

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
erlangash_authentication @ 4.4.9 (fixes >= 4.1.0, < 4.4.9)—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

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFix by version rangeDependents
ash_authentication4.1.0 ... 4.4.8 (31 versions)
  • 4.1.0 up to 4.4.9: fixed in 4.4.9
—

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 96 of 195 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-25202?
CVE-2025-25202 is a medium-severity vulnerability; its CVE record was published on February 11, 2025. Ash Authentication is an authentication framework for Elixir applications. Applications which have been bootstrapped by the igniter installer present since AshAuthentication v4.1.0 and who have used the magic link strategy or are manually revoking tokens are affected by revoked tokens being allowed…
When was the CVE record for CVE-2025-25202 published?
The CVE record for CVE-2025-25202 was published on February 11, 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 August 27, 2025; the record at its source may have been updated since.
Is CVE-2025-25202 actively exploited?
CVE-2025-25202 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-25202?
CVE-2025-25202 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2025-25202?
A fix for CVE-2025-25202 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-25202

Explore →

Is Your Infrastructure Affected by CVE-2025-25202?

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

Book a Demo →Browse All CVEs