CVE-2026-53425: dropbox samly · Insufficient Verification of Data Authenticity
Affects dropbox samlySource CVE Database V5
Not known to be exploited · CVSS 7.6 High.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dropboxsamly | Affected
| Fixed in– |
| dropboxsamly | Affected
| Fixed in– |
| handnot2samly | Affected
| Fixed in– |
Hexsamlypkg:hex/samlyOther threats | Affected
| Fixed in– |
CPE configurations (2)
cpe:2.3:a:dropbox:samly:*:*:*:*:*:*:*:*cpe:2.3:a:handnot2:samly:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, users of samly should be aware of this verification gap and consider additional controls or mitigations at the application or identity provider level to detect or prevent misuse of SAML responses with mismatched InResponseTo attributes.
Description
CVE-2026-53425 is a vulnerability in Dropbox's samly library that causes insufficient verification of data authenticity in SAML responses. The vulnerability allows an attacker to establish an authenticated session using a SAML response that the service provider never requested. This occurs because the library does not verify the InResponseTo attribute in the SAML response against the original AuthnRequest ID, violating SAML 2.0 Core requirements. Exploitation requires a valid signed assertion from the trusted IdP and a RelayState matching the victim's session.