{"answers":{"affected":"1 open source package ship an affected version, including samly.","exploited":"There is no known exploitation of CVE-2026-53425 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53425 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53425 is a high-severity authentication bypass vulnerability in dropbox samly, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-53425 and fix it if it is affected.\n\nWhat it is: CVE-2026-53425 is a high-severity authentication bypass vulnerability in dropbox samly, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-53425 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- samly (Hex): affected from 0.3.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53425/ (Markdown: https://insights.sbomify.com/CVE-2026-53425/index.md)","id":"CVE-2026-53425","markdown":"https://insights.sbomify.com/CVE-2026-53425/index.md","name":"CVE-2026-53425","record":{"aliases":["EEF-CVE-2026-53425","GHSA-4mhx-38g6-r4wq"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir SAML library","requires_auth":"none","summary":"Attackers can hijack user sessions by replaying valid SAML responses because the library fails to validate the InResponseTo field against the original request.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"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.\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.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Missing InResponseTo validation in Samly allows acceptance of unsolicited SAML responses","id":"CVE-2026-53425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Atom-table exhaustion denial-of-service via JSON parse_document in MDEx","id":"CVE-2026-53426"},"packages":[{"ecosystem":"Hex","fixed":[],"introduced":["0.3.0"],"last_affected":[],"package":"samly","purl":"pkg:hex/samly","source":"EEF-CVE-2026-53425"}],"prev":{"headline":"Missing one-time-use enforcement in Samly allows replay of SAML bearer assertions","id":"CVE-2026-53424"},"products":["samly"],"published":"2026-08-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["dropbox","handnot2"]},"summary":"Attackers can hijack user sessions by replaying valid SAML responses because the library fails to validate the InResponseTo field against the original request.","url":"https://insights.sbomify.com/CVE-2026-53425/"}