CVE-2025-54419Disclosure

LOWCVSS 10.0 · CRITICAL

Signal is active with 2 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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.

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-287CWE-347

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

2 mentions across 1 observed day

What's happening

Technical details provided in 1 signal
Disclosure: 1 classified signal
General: 1 classified signal
2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d

Signal classification2 categories

Disclosure

150.0%

General

150.0%

Referenced assets1 URL

By indicator

https://cvebrief.com/cve/CVE-2025-54419/

Full discourse2 posts

CVE Brief@DailyCVEBrief92d
Disclosure
LOOK BACK — Last July, node-saml shipped a CVSS 10 auth bypass. It verified the signature on one part of a SAML response, then read the username from an unsigned part. XML Signature Wrapping, the bug SAML libraries keep re-shipping. CVE-2025-54419, a year on. https://t.co/n6O1TlmDX3
Post summary
The tweet highlights CVE‑2025‑54419, an auth bypass in node‑saml caused by XML Signature Wrapping: the library verifies one signed part of a SAML response but trusts an unsigned username field. No PoC, active exploitation, or patch information is presented.
1000041
22 followersView on X
CVE Brief@DailyCVEBrief92d
General
Full Look Back writeup: why the signature math was never broken, why this exact bug keeps recurring across python3-saml, ruby-saml and xml-crypto, and what still hasn't happened a year later: https://cvebrief.com/cve/CVE-2025-54419/ https://t.co/vXOnkp7V3u
Post summary
The tweet links to a writeup on CVE‑2025‑54419, discussing its recurring signature math bug across multiple SAML libraries, but provides no direct exploit, patch or technical detail information.
0000040
22 followersView on X

Explore more

Back to dashboard