CVE-2026-81318

Low

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.

SeverityLow
CVSS2.1
Exploit probability—
ProductAsh-project Ash Sql
PublishedAug 30, 2026
First seenAug 30, 2026

How to fix

Update
  • ash-project ash_sql0.7.1, 3d95478cc9e1d5bfaf6144fe9b9793f29e5ab889 or later

Affected products

ProductAffected versionsFixed in
ash-project ash_sql0.1.0 ≤ v < 0.7.1, dd092ed273dec7bd2194352f24a39229fc8ae68b ≤ v < 3d95478cc9e1d5bfaf6144fe9b9793f29e5ab8890.7.1, 3d95478cc9e1d5bfaf6144fe9b9793f29e5ab889

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.