Distinct-query aggregate drops the tenant schema prefix, leaking across tenants in AshSql (CVE-2026-81318) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-81318

Distinct-query aggregate drops the tenant schema prefix, leaking across tenants in AshSql

Answer in brief

CVE-2026-81318 records a Unknown severity vulnerability in Distinct-query aggregate drops the tenant schema prefix, leaking across tenants 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 <3d95478cc9e1d5bfaf6144fe9b9793f29e5ab889	3d95478cc9e1d5bfaf6144fe9b9793f29e5ab889

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 3d95478cc9e1d5bfaf6144fe9b9793f29e5ab889 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 in a schema-based multitenant application to receive aggregate values computed from another tenant's rows. When an aggregate is computed over a distinct query, AshSql.AggregateQuery.add_single_aggs/5 rebuilds the outer query from query.from.source alone, which is only the {table, schema} tuple and does not carry query.prefix or query.from.prefix. For strategy(:context) multitenancy those hold the tenant schema, so the rebuilt outer query reads the repo's default schema while the inner correlated subquery still reads the tenant schema, and the two are joined only on primary key. The aggregate, and any relationship join added off the prefix-less binding, is then computed against the wrong tenant's rows. The neighbouring limit and exists branches instead wrap the query with subquery/1, which preserves the prefix. This issue affects ash_sql: from 0.1.0 before 0.7.1.

Quoted source text, attributed separately from HOL analysis.