CVE-2025-54419

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2025-07-28. NVD baseline CVSS 10.0; sources differ by 0.0.

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

Also known asEUVD-2025-22950 (ENISA EUVD) · GHSA-4mxg-3p6v-xgq3 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A SAML library not dependent on any frameworks that runs in Node. In version 5.0.1, Node-SAML loads the assertion from the (unsigned) original response document. This is different than the parts that are verified when checking signature. This allows an attacker to modify authentication details within a valid SAML assertion. For example, in one attack it is possible to remove any character from the SAML assertion username. To conduct the attack an attacker would need a validly signed document from the identity provider (IdP). This is fixed in version 5.1.0.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-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-11-01). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 28, 2025

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Nov 1, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Node-SAML SAML Signature Verification Vulnerability · Advisory · node-saml/node-saml · GitHub

https://github.com/node-saml/node-saml/security/advisories/GHSA-4mxg-3p6v-xgq3
GitHub release Patch Available

v5.1.0

Patch available: node-saml/node-saml v5.1.0

https://github.com/node-saml/node-saml/releases/tag/v5.1.0
GitHub commit Patch Available

commit 31ead9411ebc (node-saml/node-saml)

Patch available: node-saml/node-saml v5.1.0 (contains commit 31ead9411ebc)

https://github.com/node-saml/node-saml/commit/31ead9411ebc3e2385086fa9149b6c17732bca10

Vendor Advisories for CVE-2025-54419(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:1.7.0-17549364702025-08-19redhat
npm@node-saml/node-saml @ 5.1.0 (fixes <= 5.0.1)—ghsa
npmpassport-saml—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

(3 across 1 ecosystem)
npm(3)
PackageVulnerable rangeFix by version rangeDependents
@node-saml/node-saml—
  • every version up to 5.1.0: fixed in 5.1.0
—
@node-saml/passport-saml—
  • every version up to 5.1.0: fixed in 5.1.0
—
passport-saml—
  • every version through 3.2.4: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 81× 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 281 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 185 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-54419?
CVE-2025-54419 is a critical-severity vulnerability; its CVE record was published on July 28, 2025. A SAML library not dependent on any frameworks that runs in Node. In version 5.0.1, Node-SAML loads the assertion from the (unsigned) original response document. This is different than the parts that are verified when checking signature. This allows an attacker to modify authentication details…
When was the CVE record for CVE-2025-54419 published?
The CVE record for CVE-2025-54419 was published on July 28, 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-54419 actively exploited?
CVE-2025-54419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-54419?
CVE-2025-54419 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2025-54419?
A fix for CVE-2025-54419 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-54419 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-54419?

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