CVE-2025-54419
No exploitation reported by the sources we read.
- Published2025-07-28
- Fixed in5.1.0
- WeaknessCWE-287 · CWE-347
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2025-07-2820:17CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-54419?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-54419?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.1 | < 5.1.0 | 5.1.0 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.1 | < 5.1.0 | 5.1.0 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.2 | ≤ 3.2.4 | no fix published | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
@node-saml/node-saml: Node-SAML Signature Verification Vulnerability
Red Hat Security Advisory: Red Hat Developer Hub 1.7.0 release.
Fix
- Update @node-saml/node-saml to 5.1.0
- Vendor fix Red Hat Product Security RHSA-2025:14090 · 1 productFor more about Red Hat Developer Hub, see References links
- Workaround from the vendor Red Hat Product Security RHSA-2025:14090 · 3 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
- Published
- 2025-07-28
- Last Modified
- 2026-06-17
- NVD status
- Deferred
Frequently asked questions
What is CVE-2025-54419?
Is CVE-2025-54419 actively exploited?
What is the CVSS score for CVE-2025-54419?
Running @node-saml/node-saml? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.