Skip to content
Threat Brief

← All advisories

CVE-2026-53425

High 7.6No known exploitationFix status unknown

Missing InResponseTo validation in Samly allows acceptance of unsolicited SAML responses

Record last updated

CVSS score

7.6

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 19% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Weakness: CWE-345

Patching and mitigation

Patch status
Unknown: no source documents a fix
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
dropboxsamly0.3.0Not documentedCVE Program
dropboxsamly8a5bb1b4a4753d05470da2036323477f63cfdf4cNot documentedCVE Program
handnot2samly8a5bb1b4a4753d05470da2036323477f63cfdf4cNot documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

Vendor guidance and references