CVE-2026-82748: CWE-863 Incorrect Authorization in ash-project ash
Description
Incorrect Authorization vulnerability in ash-project ash authorizes an aggregate under one read action while computing it under another, so an aggregate can run with policies that do not match the action it was authorized against. Ash.Actions.Aggregate groups aggregates by their {authorize?, read_action} and authorizes each group under that read action, but when building the data query it selected the action as opts[:action] || read_action || <primary read> (lib/ash/actions/aggregate.ex). When a caller passed an :action option, the aggregate query ran under that action while authorization had been computed for the group's own read_action. If the run action's read policies are more permissive than the authorized one, the aggregate (a count or sum) is computed over records the authorized action's policies would have excluded, disclosing information about data the actor cannot read. The fix runs the aggregate under the same read_action it is authorized against. This issue affects ash: from 3.5.13 before 3.32.2.
CVSS v4.0
Score 2.1low
Affected software
ash-project
ash
ash-project
ash
cpe:2.3:a:ash-project:ash:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because Ash.Actions.Aggregate groups aggregates by their {authorize?, read_action} and authorizes each group under that read action. However, when building the data query, the action used can differ from the authorized read_action if an :action option is passed. This causes the aggregate query to run under a potentially more permissive action than the one used for authorization, allowing aggregates (such as counts or sums) to include records that the authorized action's policies would exclude. The fix involves ensuring the aggregate runs under the same read_action it was authorized against. This affects ash versions >=3.5.13 and <3.32.2.
Potential Impact
An attacker with access to the aggregate functionality may obtain aggregate data computed over records they are not authorized to read, leading to unauthorized disclosure of information. The impact is limited to data exposure through aggregates and does not allow direct access to individual records. The CVSS score of 2.1 reflects a low severity due to the limited scope and complexity of exploitation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability is fixed by running the aggregate under the same read_action it is authorized against. Until a patch is available, avoid passing differing :action options to aggregate queries or restrict aggregate usage to trusted users.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-08-31T01:00:09.774Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a964f9bacd9273b4930b0f2
Added to database: 09/01/2026, 04:07:55 UTC
Last enriched: 09/07/2026, 14:47:03 UTC
Last updated: 10/16/2026, 06:48:19 UTC
Views: 93
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.