Description (CNA)
Incorrect Authorization vulnerability in ash-project ash_sql allows a caller to receive an aggregate value computed over rows a more restrictive filter should have excluded, disclosing counts, sums, or lists across an authorization or tenancy boundary. AshSql.Aggregate.different_queries?/2 reports two aggregate queries as different only when their filter and their sort both differ. Aggregate queries rarely carry a sort, so two aggregates that share a name but carry entirely different filters compare as identical. The colliding aggregate keeps its name and is treated as already computed, and select_aggregates returns the first-registered variant's value. The same name reaches the builder twice with different filters when actor or tenant context is stamped into each aggregate's query, so a narrowly filtered aggregate can be served the value of a previously registered broad one. This issue affects ash_sql: from 0.1.0 before 0.7.1.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| ash-project / ash_sql | affected 0.1.0 before 0.7.1 |
| ash-project / ash_sql | affected dd092ed273dec7bd2194352f24a39229fc8ae68b before 4b95468e5434a3526571414219719c9518be6694 |
CWE
CWE-863
References
- https://github.com/ash-project/ash_sql/security/advisories/GHSA-v7pf-wjxc-7j5m
- https://cna.erlef.org/cves/CVE-2026-81316.html
- https://osv.dev/vulnerability/EEF-CVE-2026-81316
- https://github.com/ash-project/ash_sql/commit/4b95468e5434a3526571414219719c9518be6694
ADP enrichment
No English description supplied.