Distinct-query aggregate drops the tenant schema prefix, leaking across tenants in AshSql
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| ash-project | ash_sql | 0.1.0 to before 0.7.1 | 0.7.1 | Patch available | CNA |
- ash_sql Vendorash-project Affected 0.1.0 to before 0.7.1 Fixed in 0.7.1 Patch available CNA
CPE names CNA · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:* | — | — | — |
- cpe:2.3:a:ash-project:ash_sql:*:*:*:*:*:*:*:* Versions — — ·—
Remediation
- Fix · CNA ash_sql (ash-project) Fixed in 0.7.1
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
ash-project ash_sql 0.7.1
5 records Highest priority Priority MEDIUM 5 MEDIUM
Other records, highest priority first
- TI-2026-54013 exists/2 predicate silently dropped on limited relationships with a parent() filter in AshSqlPriority MEDIUM 60
- TI-2026-56146 Same-named aggregates with differing filters are conflated in AshSqlPriority MEDIUM 44
- TI-2026-55460 SQL string_trim removes only spaces, diverging from in-memory trimming in AshSqlPriority MEDIUM 44
Timeline
- 2026-10-02 Threatist record created from CVE-2026-81318
References
More ash-project vulnerabilities
- TI-2026-56298 Query-complexity limit bypass via first/last pagination arguments in AshGraphql enables denial of service CVSS 4.0HIGH 8.7
- TI-2026-52572 Unbounded atom creation from client-supplied RPC field names in AshTypescript field formatter CVSS 4.0HIGH 8.7
- TI-2026-57010 Path traversal in AshAdmin file uploads via unsanitized client filename CVSS 4.0HIGH 8.3
- TI-2026-26840 Ash Framework: Ash.Type.Module.cast_input/2 atom exhaustion via unchecked Module.concat allows BEAM VM crash CVSS 4.0HIGH 8.2
- TI-2026-54252 EEx template evaluation of prompt content in AshAi enables remote code execution CVSS 4.0HIGH 8.9
- TI-2026-54208 Stored XSS in AshAdmin relationship typeahead via unescaped label_field content CVSS 4.0HIGH 8.4
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences