CVE-2026-53424: handnot2 samly · Authentication Bypass by Capture-replay
Affects handnot2 samlySource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical.
Data as of 19 Nov 2026, 09:04 UTC
Thin evidence
One scorer or none| CNA (EEF) | CVSS 4.0 | 9.1 |
|---|
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% 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:N/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 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| samlyhandnot2/samly | Affected
| Fixed in– |
| dropboxsamly | Affected
| Fixed in– |
| samlydropbox/samly | Affected
| Fixed in– |
Hexsamlypkg:hex/samlyOther threats | Affected
| Fixed in– |
CPE configurations (2)
cpe:2.3:a:handnot2:samly:*:*:*:*:*:*:*:*cpe:2.3:a:dropbox:samly:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should monitor the vendor advisory for updates. Until a fix is released, consider implementing external controls to detect and prevent replay attacks on SAML assertions or avoid using affected versions if possible.
Description
Authentication Bypass by Capture-replay vulnerability in dropbox samly allows an attacker to authenticate as the subject of a captured SAML assertion by resubmitting it. Samly.Helper.decode_idp_auth_resp/3 in lib/samly/helper.ex calls esaml_sp:validate_assertion/2, whose default duplicate detector is a no-op. The /3 arity accepting a DuplicateFun exists in esaml and implements the check, but Samly never calls it and offers no configuration to supply one, so the SAML 2.0 Web Browser SSO Profile requirement that a bearer assertion be used once is unenforced. An attacker holding a valid SAMLResponse obtained from the network, from browser history, or from logs can submit the identical bytes repeatedly until the assertion's NotOnOrAfter passes, each time establishing a session as the assertion's subject. This issue affects samly: from 0.3.0 onward.
References
- cna.erlef.org/cves/CVE-2026-53424.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-53424 (opens in a new tab)
- github.com/handnot2/samly/commit/8a5bb1b4a4753d05470da2036323477f63cfdf4c (opens in a new tab)
- github.com/dropbox/samly/commit/8a5bb1b4a4753d05470da2036323477f63cfdf4c (opens in a new tab)