CVE-2026-101028: Ash incorrect authorization in aggregate queries

CVE-2026-101028 · Severity: info · Published 2026-10-09

Ash, a data framework for Elixir applications, fails to apply read policies when performing count, exists, or aggregate operations. This allows an attacker to probe for the existence and values of related records they should not have access to by testing conditions one query at a time, potentially exposing sensitive data.

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

Quick answers

Is CVE-2026-101028 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-101028 being exploited in the wild.
How severe is CVE-2026-101028?
Informational severity, published 9 October 2026.
Which products and versions are affected?
Ash-Project Ash 2.6.0 through 3.34.5.
Is there a fix for CVE-2026-101028?
Yes: fixed in 3.34.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-101028 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-101028?
Check whether you run Ash-Project Ash 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.

How to fix

  • Fixed in: 3.34.6

Technical details

The Ash.Actions.Aggregate.run/4 function applies only the root resource's read policy before executing aggregate queries, skipping the related resource read policies that are normally applied during read operations. An attacker with query input capability can craft filters or sorts that reach hidden related records and infer attribute values through repeated count or exists calls across relationships.

Affected products

  • ash-project Ash 2.6.0 through 3.34.5

Timeline

  • 2026-10-09: disclosed

References

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