{"containers":{"cna":{"affected":[{"collectionURL":"https://repo.hex.pm","cpes":["cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*"],"defaultStatus":"unaffected","modules":["'Elixir.Ash.Actions.ManagedRelationships'","'Elixir.Ash.Changeset'"],"packageName":"ash","packageURL":"pkg:hex/ash","product":"ash","programFiles":["lib/ash/actions/managed_relationships.ex","lib/ash/changeset/changeset.ex"],"programRoutines":[{"name":"'Elixir.Ash.Actions.ManagedRelationships':setup_managed_belongs_to_relationships/3"},{"name":"'Elixir.Ash.Changeset':manage_relationship/4"}],"repo":"https://github.com/ash-project/ash","vendor":"ash-project","versions":[{"lessThan":"3.31.1","status":"affected","version":"1.52.0-rc.11","versionType":"semver"}]},{"collectionURL":"https://github.com","cpes":["cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*"],"defaultStatus":"unaffected","modules":["'Elixir.Ash.Actions.ManagedRelationships'","'Elixir.Ash.Changeset'"],"packageName":"ash-project/ash","packageURL":"pkg:github/ash-project/ash","product":"ash","programFiles":["lib/ash/actions/managed_relationships.ex","lib/ash/changeset/changeset.ex"],"programRoutines":[{"name":"'Elixir.Ash.Actions.ManagedRelationships':setup_managed_belongs_to_relationships/3"},{"name":"'Elixir.Ash.Changeset':manage_relationship/4"}],"repo":"https://github.com/ash-project/ash","vendor":"ash-project","versions":[{"lessThan":"09f42593035bceb0f6153dd7ee45cc49d108300a","status":"affected","version":"571c138140e71cea24005189f45d7a63c8d2ed20","versionType":"git"}]}],"configurations":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>A <code>belongs_to</code> relationship must be managed with <code>manage_relationship</code> using <code>on_lookup: :relate</code>, and the lookup value must come from client input.</p>"},{"base64":false,"type":"text/markdown","value":"A `belongs_to` relationship must be managed with `manage_relationship` using `on_lookup: :relate`, and the lookup value must come from client input."}],"value":"A belongs_to relationship must be managed with manage_relationship using on_lookup: :relate, and the lookup value must come from client input."}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*","versionEndExcluding":"3.31.1","versionStartIncluding":"1.52.0-rc.11","vulnerable":true}],"negate":false,"operator":"OR"}],"operator":"AND"}],"credits":[{"lang":"en","type":"finder","value":"Jisung Chae"},{"lang":"en","type":"remediation developer","value":"Zach Daniel"},{"lang":"en","type":"analyst","value":"Jonatan Männchen / EEF"}],"descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>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.</p>\n<p>When <code>manage_relationship</code> is used with <code>on_lookup: :relate</code> on a <code>belongs_to</code> relationship, the client-supplied lookup value is passed to <code>Ash.Query.filter/2</code> 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 <code>Ash.Query.limit(1)</code>, leaving <code>Ash.read_one/2</code> 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.</p>\n<p>This issue affects ash: from 1.52.0-rc.11 before 3.31.1.</p>"},{"base64":false,"type":"text/markdown","value":"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."}],"value":"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."}],"impacts":[{"capecId":"CAPEC-116","descriptions":[{"lang":"en","value":"CAPEC-116 Excavation"}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"PRESENT","attackVector":"LOCAL","baseScore":2.1,"baseSeverity":"LOW","privilegesRequired":"NONE","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"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","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"LOW","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-943","description":"CWE-943 Improper Neutralization of Special Elements in Data Query Logic","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-08-09T18:17:07.321Z","orgId":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db","shortName":"EEF"},"references":[{"tags":["related","vendor-advisory"],"url":"https://github.com/ash-project/ash/security/advisories/GHSA-vvp6-3wv6-833j"},{"tags":["related"],"url":"https://cna.erlef.org/cves/CVE-2026-70395.html"},{"tags":["related"],"url":"https://osv.dev/vulnerability/EEF-CVE-2026-70395"},{"tags":["patch"],"url":"https://github.com/ash-project/ash/commit/09f42593035bceb0f6153dd7ee45cc49d108300a"}],"source":{"discovery":"EXTERNAL"},"title":"Predicate injection in manage_relationship belongs_to lookup discloses secret lookup keys in Ash"}},"cveMetadata":{"assignerOrgId":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db","assignerShortName":"EEF","cveId":"CVE-2026-70395","datePublished":"2026-08-09T18:17:07.321Z","dateReserved":"2026-08-04T14:30:01.369Z","dateUpdated":"2026-08-09T18:17:07.321Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"}