Same-named aggregates with differing filters are conflated in AshSql (CVE-2026-81316) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-81316

Same-named aggregates with differing filters are conflated in AshSql

Answer in brief

CVE-2026-81316 records a Unknown severity 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_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.

Published Aug 30, 2026Updated Aug 30, 2026Source checked Aug 30, 2026First seen by HOL Aug 30, 2026Material review Aug 30, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps ash-project/ash_sql (generic), ash-project/ash_sql (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ash-project/ash_sqlgeneric	>=0.1.0 <0.7.1	0.7.1
ash-project/ash_sqlgeneric	>=dd092ed273dec7bd2194352f24a39229fc8ae68b <4b95468e5434a3526571414219719c9518be6694	4b95468e5434a3526571414219719c9518be6694

Recommended response

Check inventory. Check lockfiles and deployed manifests for ash-project/ash_sql, ash-project/ash_sql.
Review the reported fix. Update ash-project/ash_sql to 0.7.1; ash-project/ash_sql to 4b95468e5434a3526571414219719c9518be6694 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 30, 2026

Sources and claim methodology

Upstream source description

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.