CVE-2025-54419: Node-SAML SAML Signature Verification Vulnerability
(updated )
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.
References
- github.com/advisories/GHSA-4mxg-3p6v-xgq3
- github.com/node-saml/node-saml
- github.com/node-saml/node-saml/commit/31ead9411ebc3e2385086fa9149b6c17732bca10
- github.com/node-saml/node-saml/releases/tag/v5.1.0
- github.com/node-saml/node-saml/security/advisories/GHSA-4mxg-3p6v-xgq3
- nvd.nist.gov/vuln/detail/CVE-2025-54419
Code Behaviors & Features
Detect and mitigate CVE-2025-54419 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →