CVE-2026-70395: Predicate injection in manage_relationship belongs_to lookup discloses secret lookup keys in Ash
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.
When managerelationship is used with onlookup: :relate on a belongsto 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.readone/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.
This issue affects ash: from 1.52.0-rc.11 before 3.31.1.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-70395?
The severity of CVE-2026-70395 is rated at risk 43.
How do I fix CVE-2026-70395?
To fix CVE-2026-70395, ensure that proper input validation and escaping mechanisms are implemented in the manage_relationship function.
What software is affected by CVE-2026-70395?
CVE-2026-70395 affects the Ash framework within the ash-project.
What kind of vulnerability is CVE-2026-70395?
CVE-2026-70395 is classified as an Improper Neutralization of Special Elements in Data Query Logic.
What impact does CVE-2026-70395 have on security?
CVE-2026-70395 allows attackers to forge records and disclose secret lookup keys, potentially leading to unauthorized access.