Vulnerability EEF-CVE-2026-53425

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
3 months ago
August 20, 2026 at 05:26 PM UTC
Missing InResponseTo validation in Samly allows acceptance of unsolicited SAML responses
0.4.0 - 1.0.0-rc.0 and 1.0.0-rc.1 and 1.0.0 - 1.4.0
0.4.0 - 1.0.0-rc.0 and 1.0.0-rc.1 and 1.0.0 - 1.4.0

Summary

Missing InResponseTo validation in Samly allows acceptance of unsolicited SAML responses

Details

Summary

Insufficient Verification of Data Authenticity vulnerability in dropbox samly allows an attacker to establish an authenticated session using a SAML response the service provider never requested.

Samly.SPHandler.validate_authresp/3 in lib/samly/sp_handler.ex validates a SAML response for the SP-initiated flow by comparing only the RelayState value, the IdP identifier, and the presence of a target URL held in the session. It never compares SubjectConfirmationData/@InResponseTo against the ID of the AuthnRequest the service provider issued, and that request ID is never persisted, so no comparison is possible. SAML 2.0 Core section 4.1.4.3 requires a service provider to reject a response whose InResponseTo does not match a request it made. The underlying esaml library checks status, signature, recipient, audience, and staleness, but likewise never inspects InResponseTo, so nothing else closes the gap. Exploitation requires a validly signed assertion from the trusted IdP, which an attacker can obtain for their own account, and a RelayState matching the victim's session; the assertion signature itself remains intact, so this is not a signature-forgery issue.

This issue affects samly: from 0.3.0 onward.

Impacted packages

Timeline

Published
3 months ago
August 20, 2026 at 05:26 PM UTC
Last Modified
1 day ago
November 20, 2026 at 05:23 PM UTC