Answer in brief
CVE-2026-82748 records a Low severity (CVSS 2.1) vulnerability in Ash.Actions.Aggregate authorizes an aggregate under one action but computes it under another. The current sources do not mark it as known exploited. The current feed maps ash-project/ash (generic), ash-project/ash (generic), ash-project/ash-project/ash (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 2.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ash-project/ash (generic), ash-project/ash (generic), ash-project/ash-project/ash (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ashgeneric | >=d2e99980380cad610dbab3c4167e85323244bc71 <2d9b78b87d2dc72885a8aa1d660b478d42f749f7 | 2d9b78b87d2dc72885a8aa1d660b478d42f749f7 |
| ash-project/ashgeneric | >=3.5.13 <3.32.2 | 3.32.2 |
| ash-project/ash-project/ashgeneric | >=d2e99980380cad610dbab3c4167e85323244bc71 <2d9b78b87d2dc72885a8aa1d660b478d42f749f7 | 2d9b78b87d2dc72885a8aa1d660b478d42f749f7 |
Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.