Skip to content
Fencer Intel
critical 10.0

CVE-2025-54419 json

Node-SAML Contains SAML Signature Verification Vulnerability

published last yr. modified 4mo ago also EUVD-2025-22950 , GHSA-4mxg-3p6v-xgq3

cvss
10.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm @node-saml/node-saml 5.1.0
  • npm @node-saml/passport-saml 5.1.0

Is CVE-2025-54419 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-54419 updated cvss 7.4

@node-saml/node-saml: Node-SAML Signature Verification Vulnerability

  • Red Hat Developer Hub 1.7 rhdh 1.7.0-1754936470
    fixed: vendor fix RHSA-2025:14090
  • Red Hat Developer Hub 1 rhdh/rhdh-rhel9-operator
    not affected: component not present
  • Red Hat Developer Hub 1.7 rhdh 1.7.0-1754935808, rhdh 1.7.0-1754942441
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
GitHub 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm @node-saml/node-saml
<5.1.0
5.1.0
npm passport-saml
<=3.2.4
 no fix listed
npm @node-saml/passport-saml
<5.1.0
5.1.0

Affected products

  • node-saml node-saml

Classification

Weakness
  • CWE-287 Improper Authentication
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.