Node-SAML SAML Signature Verification Vulnerability
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). In fixing this we made sure to process the SAML assertions from only verified/authenticated contents. This will prevent future variants from coming up. Note: this is distinct from the previous xml-crypto CVEs.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-54419US | — | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/node-saml/node-samlPACKAGE
- https://github.com/node-saml/node-saml/commit/31ead9411ebc3e2385086fa9149b6c17732bca10WEB
- https://github.com/node-saml/node-saml/releases/tag/v5.1.0WEB
- https://github.com/node-saml/node-saml/security/advisories/GHSA-4mxg-3p6v-xgq3WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-54419ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan