CVE-2025-54369: Node-SAML SAML Authentication Bypass
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.
Published Jul 25, 2025 · Updated Dec 16, 2025
Affected packages
node-saml
- Ecosystem
- npm
- Affected
- <= 3.1.2
- Fixed in
- No patched version yet
- Check
npm ls node-saml
@node-saml/node-saml
- Ecosystem
- npm
- Affected
- <= 5.0.1
- Fixed in
- 5.1.0
- Check
npm ls @node-saml/node-saml
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 upgraded xml-crypto to v6.1.2 and made sure to process the SAML assertions from only verified/authenticated contents. This will prevent future variants from coming up.
Credited to ahacker1-securesaml, cjbarth.
References
- https://github.com/node-saml/node-saml/security/advisories/GHSA-m837-g268-mmv7
- https://nvd.nist.gov/vuln/detail/CVE-2025-54369
- https://github.com/node-saml/node-saml/commit/31ead9411ebc3e2385086fa9149b6c17732bca10
- https://github.com/node-saml/node-saml/releases/tag/v5.1.0
- https://github.com/advisories/GHSA-m837-g268-mmv7
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology