Answer in brief
CVE-2026-81316 records a Low severity (CVSS 2.1) vulnerability in Same-named aggregates with differing filters are conflated in AshSql. The current sources do not mark it as known exploited. The current feed maps ash-project/ash-project/ash_sql (generic), ash-project/ash_sql (generic), ash-project/ash_sql (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-project/ash_sql (generic), ash-project/ash_sql (generic), ash-project/ash_sql (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash-project/ash_sqlgeneric | >=dd092ed273dec7bd2194352f24a39229fc8ae68b <4b95468e5434a3526571414219719c9518be6694 | 4b95468e5434a3526571414219719c9518be6694 |
| ash-project/ash_sqlgeneric | >=dd092ed273dec7bd2194352f24a39229fc8ae68b <4b95468e5434a3526571414219719c9518be6694 | 4b95468e5434a3526571414219719c9518be6694 |
| ash-project/ash_sqlgeneric | >=0.1.0 <0.7.1 | 0.7.1 |
Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 30, 2026
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.
Quoted source text, attributed separately from HOL analysis.