Description (CNA)
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 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. This issue affects ash: from 1.52.0-rc.11 before 3.31.1.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| ash-project / ash | affected 1.52.0-rc.11 before 3.31.1 |
| ash-project / ash | affected 571c138140e71cea24005189f45d7a63c8d2ed20 before 09f42593035bceb0f6153dd7ee45cc49d108300a |
CWE
CWE-943
References
- https://github.com/ash-project/ash/security/advisories/GHSA-vvp6-3wv6-833j
- https://cna.erlef.org/cves/CVE-2026-70395.html
- https://osv.dev/vulnerability/EEF-CVE-2026-70395
- https://github.com/ash-project/ash/commit/09f42593035bceb0f6153dd7ee45cc49d108300a
ADP enrichment
No English description supplied.
No references supplied.