{"answers":{"affected":"1 open source package ship an affected version, including samly.","exploited":"There is no known exploitation of CVE-2026-53424 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53424 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53424 is a critical authentication bypass vulnerability in dropbox samly, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53424 and fix it if it is affected.\n\nWhat it is: CVE-2026-53424 is a critical authentication bypass vulnerability in dropbox samly, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53424 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-53424/ (Markdown: https://insights.sbomify.com/CVE-2026-53424/index.md)","id":"CVE-2026-53424","markdown":"https://insights.sbomify.com/CVE-2026-53424/index.md","name":"CVE-2026-53424","record":{"aliases":["EEF-CVE-2026-53424","GHSA-5x87-gf34-8ww7"],"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 replay captured SAML assertions to authenticate as other users due to missing one-time-use enforcement in the Samly library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"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.\n\nSamly.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.\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 one-time-use enforcement in Samly allows replay of SAML bearer assertions","id":"CVE-2026-53424","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":"Missing InResponseTo validation in Samly allows acceptance of unsolicited SAML responses","id":"CVE-2026-53425"},"packages":[{"ecosystem":"Hex","fixed":[],"introduced":["0.3.0"],"last_affected":[],"package":"samly","purl":"pkg:hex/samly","source":"EEF-CVE-2026-53424"}],"prev":{"headline":"Unauthenticated denial-of-service via BEAM atom table exhaustion in membrane_mp4_plugin","id":"CVE-2026-53423"},"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["dropbox","handnot2"]},"summary":"Attackers can replay captured SAML assertions to authenticate as other users due to missing one-time-use enforcement in the Samly library.","url":"https://insights.sbomify.com/CVE-2026-53424/"}