Node-SAML SAML Authentication Bypass
cve-program · CVE-2025-54369
PublishedNode-SAML is a SAML library not dependent on any frameworks that runs in Node. In versions 5.0.1 and below, 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. This issue is fixed in version 5.1.0.
Read the publisher's advisoryeuvd · EUVD-2025-22555
PublishedNode-SAML is a SAML library not dependent on any frameworks that runs in Node. In versions 5.0.1 and below, 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. This issue is fixed in version 5.1.0.
Read the publisher's advisorynvd · CVE-2025-54369
PublishedNode-SAML is a SAML library not dependent on any frameworks that runs in Node. In versions 5.0.1 and below, 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. This issue is fixed in version 5.1.0.
Read the publisher's advisoryosv · GHSA-m837-g268-mmv7
PublishedNode-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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-54369 · CVE overview and exploitation status
cve-program · CVE-2025-54369
- https://github.com/node-saml/node-saml/security/advisories/GHSA-m837-g268-mmv7
- https://github.com/node-saml/node-saml/commit/31ead9411ebc3e2385086fa9149b6c17732bca10
- https://github.com/node-saml/node-saml/releases/tag/v5.1.0
euvd · EUVD-2025-22555
- https://github.com/node-saml/node-saml/security/advisories/GHSA-m837-g268-mmv7
- https://github.com/node-saml/node-saml/commit/31ead9411ebc3e2385086fa9149b6c17732bca10
- https://github.com/node-saml/node-saml/releases/tag/v5.1.0
nvd · 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/node-saml/node-saml/security/advisories/GHSA-m837-g268-mmv7
osv · GHSA-m837-g268-mmv7
- 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
- https://github.com/node-saml/node-saml/releases/tag/v5.1.0
Related changes
Linked by CVE identifierNo related changes are available here.