Is CVE-2026-81316 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-81316 being exploited in the wild.

How severe is CVE-2026-81316?

Informational severity, published 30 August 2026.

Which products and versions are affected?

Ash-Project Ash Sql 0.1.0 before 0.7.1.

Is there a fix for CVE-2026-81316?

A patch was published on 2026: Version 0.7.1 available Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-81316 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-81316?

Check whether you run Ash-Project Ash Sql at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-81316: ash-project ash_sql incorrect authorization in aggregate queries

CVE-2026-81316 · Severity: info · Published 2026-08-30

AshSql is a data querying and aggregation library used in Elixir applications. A vulnerability in aggregate query handling allows attackers to bypass authorization filters and receive aggregated data (counts, sums, or lists) that should have been restricted, potentially exposing sensitive information across tenant or authorization boundaries.

Technologies: Ash-Project Ash Sql. Vendors: Ash-Project.

Quick answers

Is CVE-2026-81316 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-81316 being exploited in the wild.
How severe is CVE-2026-81316?: Informational severity, published 30 August 2026.
Which products and versions are affected?: Ash-Project Ash Sql 0.1.0 before 0.7.1.
Is there a fix for CVE-2026-81316?: A patch was published on 2026: Version 0.7.1 available Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-81316 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-81316?: Check whether you run Ash-Project Ash Sql at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in AshSql.Aggregate.different_queries?/2, which incorrectly identifies aggregate queries as identical when they share the same name but carry different filters, only comparing filter and sort criteria. When actor or tenant context is stamped into each aggregate's query, a narrowly filtered aggregate query collides with a previously registered broad aggregate, causing the library to return the first-registered (broader) value. This is a logic error in query deduplication that allows authorization contexts to be bypassed. The flaw affects versions 0.1.0 through 0.7.0; patch 0.7.1 is available.

Affected products

ash-project ash_sql 0.1.0 before 0.7.1

Timeline

2026-08-30: disclosed
2026: patched: Version 0.7.1 available

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.