Description (CNA)
Incorrect Authorization vulnerability in ash-project ash_sql allows a caller to bypass a scoping or authorization filter expressed as exists/2 over a relationship that declares both a limit (or from_many?) and a parent(...)-referencing filter or sort. AshSql.Join.related_query/3 skips the caller-supplied exists predicate for such relationships and delegates it to limit_from_many/5. When the relationship's own filter or sort references parent(...), limit_from_many/5 takes a branch that drops both the limit and the predicate, emitting a bare correlated EXISTS with no predicate. The check then matches any record that has any related row. Most severely, when the expression backs a policy (for example authorize_if expr(exists(memberships, user_id == ^actor(:id)))), the actor-scoping condition disappears and the policy passes for any actor with any related row. This issue affects ash_sql: from 0.4.1 before 0.7.1.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| ash-project / ash_sql | affected 0.4.1 before 0.7.1 |
| ash-project / ash_sql | affected e26a63b29bd7501505fafd726f14262cdc3b6629 before 865fdd4e5e70724a23b19c048e6768c31d2209ab |
CWE
CWE-863
References
- https://github.com/ash-project/ash_sql/security/advisories/GHSA-8v9m-8pxv-738c
- https://cna.erlef.org/cves/CVE-2026-77454.html
- https://osv.dev/vulnerability/EEF-CVE-2026-77454
- https://github.com/ash-project/ash_sql/commit/865fdd4e5e70724a23b19c048e6768c31d2209ab
ADP enrichment
No English description supplied.