Headline

GHSA-4mxg-3p6v-xgq3: 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.

13 hours ago

ghsa

Open in Source

#vulnerability #nodejs #git #auth

GitHub Advisory Database
GitHub Reviewed
CVE-2025-54419

Node-SAML SAML Signature Verification Vulnerability

Critical severity GitHub Reviewed Published Jul 28, 2025 in node-saml/node-saml • Updated Jul 28, 2025

Package

npm @node-saml/node-saml (npm)

Affected versions

= 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).

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