Incorrect Authorization vulnerability in ash-project ash allows an actor to infer data in related records they cannot read via Ash.count/2, Ash.exists/2 and Ash.aggregate/3.
Ash.Actions.Aggregate.run/4 (lib/ash/actions/aggregate.ex) applied only the root resource's read policy before running the aggregate query. The read path also applies each related resource's read policy to filter and sort references that cross a relationship, directly (for example comments.body) or through an aggregate over one, but the aggregate path skipped that step. A caller whose filter or sort reaches these functions, for example through Ash.Query.filter_input/2, an ash_lua script, or an AshAi tool offering count or exists results, can test conditions against related rows hidden from them and recover their existence and attribute values one query at a time. Ash.read/2 and its page counts are not affected.
This issue affects ash: from 2.6.0 before 3.34.6.
CVSS
No CVSS.
References
Configurations
No configuration.
History
09 Oct 2026, 18:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/ash-project/ash/security/advisories/GHSA-xj24-8f5c-pp5p - |
09 Oct 2026, 07:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-09 07:17
Updated : 2026-10-09 18:17
NVD link : CVE-2026-101028
Mitre link : CVE-2026-101028
CVE.ORG link : CVE-2026-101028
JSON object : View
Products Affected
No product.
CWE
CWE-863
Incorrect Authorization
