{"answers":{"affected":"1 open source package ship an affected version, including ash.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82744 exists.","fix":"Upgrade ash to 3.32.2 or later.","what":"CVE-2026-82744 is a low-severity vulnerability in ash-project ash, published on 1 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82744 and fix it if it is affected.\n\nWhat it is: CVE-2026-82744 is a low-severity vulnerability in ash-project ash, published on 1 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82744 exists.\n\nAffected packages and fixed versions:\n- ash (Hex): affected from 3.0.0-rc.17; fixed in 3.32.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-2026-82744/ (Markdown: https://insights.sbomify.com/CVE-2026-82744/index.md)","id":"CVE-2026-82744","markdown":"https://insights.sbomify.com/CVE-2026-82744/index.md","name":"CVE-2026-82744","record":{"aliases":["EEF-CVE-2026-82744","GHSA-3xq4-m876-fr88"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir Ash framework","requires_auth":"none","summary":"Attackers can bypass security-relevant changes in Ash.Reactor by triggering exceptions in validation guards, causing the system to fail open and skip critical steps.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-636","name":"Not Failing Securely"}],"description":"Not Failing Securely (Failing Open) vulnerability in ash-project ash skips an Ash.Reactor change when the guard controlling it raises, so a change meant to run does not.\n\nAn Ash.Reactor change step can be gated by where validations that decide whether the change runs. Ash.Reactor.ChangeStep (lib/ash/reactor/steps/change_step.ex) evaluated those guards in apply_where_clauses/3, and apply_validation rescued any exception into {:error, error}. The reduce treated that identically to a guard whose condition was simply not met and bypassed the change. So when a guard raises (for example on attacker-influenced input), a change that enforces a security-relevant modification is skipped rather than failing the step. The fix distinguishes a raised exception (now {:raised, error}) and halts the step with an error, failing closed.\n\nThis issue affects ash: from 3.0.0-rc.17 before 3.32.2.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Ash.Reactor change step fails open, skipping a change when its where guard raises","id":"CVE-2026-82744","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"ETS and Mnesia data layers overwrite an existing record on create instead of enforcing primary-key uniqueness","id":"CVE-2026-82745"},"packages":[{"ecosystem":"Hex","fixed":["3.32.2"],"introduced":["3.0.0-rc.17"],"last_affected":[],"package":"ash","purl":"pkg:hex/ash","source":"EEF-CVE-2026-82744"}],"prev":{"headline":"Ash.Actions.Read.AsyncLimiter busy-spins a scheduler while awaiting slow async reads","id":"CVE-2026-82743"},"products":["ash"],"published":"2026-09-01","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["ash-project"]},"summary":"Attackers can bypass security-relevant changes in Ash.Reactor by triggering exceptions in validation guards, causing the system to fail open and skip critical steps.","url":"https://insights.sbomify.com/CVE-2026-82744/"}