{"answers":{"affected":"3 open source packages ship an affected version, including ash.","exploited":"There is no known exploitation of CVE-2025-48043 in the wild and no public exploit code.","fix":"Upgrade ash to 3.6.2 or later.","what":"CVE-2025-48043 is a high-severity authentication bypass vulnerability in ash-project ash, published on 10 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48043 and fix it if it is affected.\n\nWhat it is: CVE-2025-48043 is a high-severity authentication bypass vulnerability in ash-project ash, published on 10 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48043 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ash (Hex): affected all versions; fixed in 3.6.2\n- ash (Hex): affected all versions; fixed in 3.6.2\n- ash (Hex): affected from 0.1.1; fixed in 3.6.2\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-2025-48043/ (Markdown: https://insights.sbomify.com/CVE-2025-48043/index.md)","id":"CVE-2025-48043","markdown":"https://insights.sbomify.com/CVE-2025-48043/index.md","name":"CVE-2025-48043","record":{"aliases":["EEF-CVE-2025-48043","GHSA-7r7f-9xpj-jmr7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir authorization library","requires_auth":"low_privilege","summary":"Attackers can bypass authentication and authorization policies in the ash library due to incorrect filter application logic.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Incorrect Authorization vulnerability in ash-project ash allows Authentication Bypass.\n\nThis issue affects ash: from 0.1.1 before 3.6.2.","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":true,"headline":"Bypass and runtime policies that can never pass may be incorrectly applied in filter authorization","id":"CVE-2025-48043","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":3,"n_references":5,"next":{"headline":"Authorization bypass when bypass policy condition evaluates to true","id":"CVE-2025-48044"},"packages":[{"ecosystem":"Hex","fixed":["3.6.2"],"introduced":["0"],"last_affected":[],"package":"ash","purl":null,"source":"GHSA-7r7f-9xpj-jmr7"},{"ecosystem":"Hex","fixed":["3.6.2"],"introduced":["0"],"last_affected":[],"package":"ash","purl":"pkg:hex/ash","source":"GHSA-7r7f-9xpj-jmr7"},{"ecosystem":"Hex","fixed":["3.6.2"],"introduced":["0.1.1"],"last_affected":[],"package":"ash","purl":"pkg:hex/ash","source":"EEF-CVE-2025-48043"}],"prev":{"headline":"Before action hooks may execute in certain scenarios despite a request being forbidden","id":"CVE-2025-48042"},"products":["ash"],"published":"2025-10-10","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-09-22","vendors":["ash-project"]},"summary":"Attackers can bypass authentication and authorization policies in the ash library due to incorrect filter application logic.","url":"https://insights.sbomify.com/CVE-2025-48043/"}