{"answers":{"affected":"1 open source package ship an affected version, including ash.","exploited":"There is no known exploitation of CVE-2026-70395 in the wild and no public exploit code.","fix":"Upgrade ash to 3.31.1 or later.","what":"CVE-2026-70395 is a low-severity SQL injection vulnerability in ash-project ash, published on 9 Aug 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-70395 and fix it if it is affected.\n\nWhat it is: CVE-2026-70395 is a low-severity SQL injection vulnerability in ash-project ash, published on 9 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-70395 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ash (Hex): affected from 1.52.0-rc.11; fixed in 3.31.1\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-70395/ (Markdown: https://insights.sbomify.com/CVE-2026-70395/index.md)","id":"CVE-2026-70395","markdown":"https://insights.sbomify.com/CVE-2026-70395/index.md","name":"CVE-2026-70395","record":{"aliases":["EEF-CVE-2026-70395","GHSA-vvp6-3wv6-833j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir Ash framework","requires_auth":"none","summary":"Attackers can inject filter predicates into relationship lookups to recover secret lookup keys via an oracle, exposing sensitive data.","user_interaction":"not_required","vuln_class":"sql_injection"},"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:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"description":"Improper Neutralization of Special Elements in Data Query Logic vulnerability in ash-project ash allows an attacker to forge a relationship to a record they cannot name, and to recover the secret value used to look it up.\n\nWhen manage_relationship is used with on_lookup: :relate on a belongs_to relationship, the client-supplied lookup value is passed to Ash.Query.filter/2 without being cast to the attribute type. A nested map submitted where a scalar is expected is therefore interpreted as a filter predicate rather than a literal, so a lookup for a specific record becomes a query for any record matching a condition. The same path omits Ash.Query.limit(1), leaving Ash.read_one/2 able to distinguish no match from one match from several, which turns comparison predicates into an oracle for the lookup value. Authorization is unaffected; the destination read policy still applies.\n\nThis issue affects ash: from 1.52.0-rc.11 before 3.31.1.","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":"Predicate injection in manage_relationship belongs_to lookup discloses secret lookup keys in Ash","id":"CVE-2026-70395","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Gitea organization repository creation token scope bypass","id":"CVE-2026-70396"},"packages":[{"ecosystem":"Hex","fixed":["3.31.1"],"introduced":["1.52.0-rc.11"],"last_affected":[],"package":"ash","purl":"pkg:hex/ash","source":"EEF-CVE-2026-70395"}],"prev":{"headline":"Memory Corruption via Integer Underflow in Message Length Validation","id":"CVE-2026-70388"},"products":["ash"],"published":"2026-08-09","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":"partial"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["ash-project"]},"summary":"Attackers can inject filter predicates into relationship lookups to recover secret lookup keys via an oracle, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-70395/"}