Skip to main content
CVE-2026-53425VulnerabilityPublished Updated

dropbox samly · Insufficient Verification of Data Authenticity Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-53425· High 7.6

Not known to be exploited · CVSS 7.6 High.

Data as of 19 Nov 2026, 12:38 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (EEF)CVSS 4.07.6
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
dropboxsamlyAffected
  • >=0.3.0
Fixed in–
samlydropbox/samlyAffected
  • ≥ 8a5bb1b4a4753d05470da2036323477f63cfdf4c
Fixed in–
samlyhandnot2/samlyAffected
  • ≥ 8a5bb1b4a4753d05470da2036323477f63cfdf4c
Fixed in–
Hexsamlypkg:hex/samlyOther threatsAffected
  • >=0.3.0
Fixed in–

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 risk and consider additional compensating controls in their SAML authentication flows, such as verifying InResponseTo attributes externally or restricting session reuse. Monitor vendor channels for updates.

Description

A vulnerability in the samly library used by Dropbox allows attackers to establish authenticated sessions using SAML responses that were never requested by the service provider. The flaw arises because the validation process does not verify that the SAML response's InResponseTo attribute matches an AuthnRequest issued by the service provider, violating SAML 2.0 Core requirements. Exploitation requires a valid signed assertion from the trusted identity provider and a RelayState matching the victim's session.

References

Community reviews

Loading reviews…