{"id":"CVE-2026-53425","summary":"Missing InResponseTo validation in Samly allows acceptance of unsolicited SAML responses","details":"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.\n\nSamly.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.\n\nThis issue affects samly: from 0.3.0 onward.","aliases":["EEF-CVE-2026-53425"],"modified":"2026-11-20T07:45:52.023406198Z","published":"2026-08-20T17:26:35.537Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53425.json","unresolved_ranges":[{"extracted_events":[{"strategy":"StandardRange","range":[{"introduced":"0.3.0"},{"fixed":"*"},{"introduced":"8a5bb1b4a4753d05470da2036323477f63cfdf4c"},{"fixed":"*"},{"introduced":"8a5bb1b4a4753d05470da2036323477f63cfdf4c"},{"fixed":"*"}],"source":"AFFECTED_FIELD"}]}],"cna_assigner":"EEF","cwe_ids":["CWE-345"]},"references":[{"type":"WEB","url":"https://github.com"},{"type":"WEB","url":"https://osv.dev/vulnerability/EEF-CVE-2026-53425"},{"type":"WEB","url":"https://repo.hex.pm"},{"type":"ADVISORY","url":"https://cna.erlef.org/cves/CVE-2026-53425.html"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53425.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53425"},{"type":"FIX","url":"https://github.com/dropbox/samly/commit/8a5bb1b4a4753d05470da2036323477f63cfdf4c"},{"type":"FIX","url":"https://github.com/handnot2/samly/commit/8a5bb1b4a4753d05470da2036323477f63cfdf4c"},{"type":"PACKAGE","url":"https://github.com/dropbox/samly"},{"type":"PACKAGE","url":"https://github.com/handnot2/samly"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/dropbox/samly","events":[{"introduced":"0"},{"fixed":"8a5bb1b4a4753d05470da2036323477f63cfdf4c"}],"database_specific":{"extracted_events":[{"range":[{"fixed":"8a5bb1b4a4753d05470da2036323477f63cfdf4c"}],"source":"REFERENCES_COMMIT"}]}}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53425.json"}},{"ranges":[{"type":"GIT","repo":"https://github.com/handnot2/samly","events":[{"introduced":"0"},{"fixed":"8a5bb1b4a4753d05470da2036323477f63cfdf4c"}],"database_specific":{"extracted_events":[{"range":[{"fixed":"8a5bb1b4a4753d05470da2036323477f63cfdf4c"}],"source":"REFERENCES_COMMIT"}]}}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53425.json"}}],"schema_version":"1.9.2","severity":[{"type":"CVSS_V4","score":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"}]}