Authentication bypass via unsigned assertion processing
Published Dec 12, 2025 · Updated May 7, 2026
Improper SAML signature verification in node-saml Node SAML before 5.1.0 allows remote attackers to alter authentication details. validatePostResponseAsync verifies one XML region but passes an assertion taken from the original unsigned response to processValidlySignedAssertionAsync. Exploitation requires a validly signed IdP document and can change the asserted username, causing the relying application to authenticate the wrong identity.
Summary
What happened
Improper SAML signature verification in node-saml Node SAML before 5.1.0 allows remote attackers to alter authentication details. validatePostResponseAsync verifies one XML region but passes an assertion taken from the original unsigned response to processValidlySignedAssertionAsync. Exploitation requires a validly signed IdP document and can change the asserted username, causing the relying application to authenticate the wrong identity.
The record
- CVE
- CVE-2025-54369
- Published
- Dec 12, 2025
- Updated
- May 7, 2026
- Vendor
- node-saml
- Product
- Node SAML
- Classifications
- CWE-287, CWE-347, T1606.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2025CVE publishedPublication date reported by the CVE source.
- May 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo