The vulnerability in ash-project ash (versions from 1.52.0-rc.11 before 3.31.1) involves improper neutralization of special elements in data query logic (CWE-943). Specifically, when manage_relationship is used with on_lookup: :relate on a belongs_to relationship, client-supplied lookup values are passed directly to Ash.Query.filter/2 without casting to the attribute type. This allows a nested map, where a scalar is expected, to be interpreted as a filter predicate rather than a literal value. Consequently, a lookup intended for a specific record becomes a query for any record matching a condition. Additionally, the query omits Ash.Query.limit(1), enabling Ash.read_one/2 to distinguish between no match, one match, or multiple matches. This behavior effectively turns comparison predicates into an oracle for the lookup value. Despite this, authorization is unaffected as the destination read policy still applies.

An attacker can forge relationships to records they cannot explicitly name and recover secret values used for lookups by exploiting the query logic flaw. However, authorization policies remain in place, preventing unauthorized data access beyond what the policy allows. The vulnerability has a low CVSS score (2.1) indicating limited impact and attack complexity.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided at this time. Users should monitor vendor communications for updates. Authorization policies remain effective, so no immediate action is required to prevent unauthorized data access beyond existing controls.