CVE-2025-54419

{"cve": {"data_type": "CVE", "references": {"reference_data": [{"url": "https://github.com/node-saml/node-saml/commit/31ead9411ebc3e2385086fa9149b6c17732bca10", "name": "https://github.com/node-saml/node-saml/commit/31ead9411ebc3e2385086fa9149b6c17732bca10", "tags": [], "refsource": ""}, {"url": "https://github.com/node-saml/node-saml/releases/tag/v5.1.0", "name": "https://github.com/node-saml/node-saml/releases/tag/v5.1.0", "tags": [], "refsource": ""}, {"url": "https://github.com/node-saml/node-saml/security/advisories/GHSA-4mxg-3p6v-xgq3", "name": "https://github.com/node-saml/node-saml/security/advisories/GHSA-4mxg-3p6v-xgq3", "tags": [], "refsource": ""}]}, "data_format": "MITRE", "description": {"description_data": [{"lang": "en", "value": "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 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). This is fixed in version 5.1.0."}]}, "problemtype": {"problemtype_data": [{"description": []}]}, "data_version": "4.0", "CVE_data_meta": {"ID": "CVE-2025-54419", "ASSIGNER": "security-advisories@github.com"}}, "impact": {}, "publishedDate": "2025-07-28T20:17Z", "configurations": {"nodes": [], "CVE_data_version": "4.0"}, "lastModifiedDate": "2025-07-28T21:15Z"}