CVE-2026-82748 Ash.Actions.Aggregate authorizes an aggregate under one action but computes it under another

Low 2.1 Published Updated

Attackers can bypass read policies to disclose aggregate data they are not authorized to view by exploiting a mismatch between authorization and query execution actions.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-82748?

CVE-2026-82748 is a low-severity missing authorization vulnerability in ash-project ash, published on 1 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

Incorrect Authorization vulnerability in ash-project ash authorizes an aggregate under one read action while computing it under another, so an aggregate can run with policies that do not match the action it was authorized against.

Ash.Actions.Aggregate groups aggregates by their {authorize?, read_action} and authorizes each group under that read action, but when building the data query it selected the action as opts[:action] || read_action || <primary read> (lib/ash/actions/aggregate.ex). When a caller passed an :action option, the aggregate query ran under that action while authorization had been computed for the group's own read_action. If the run action's read policies are more permissive than the authorized one, the aggregate (a count or sum) is computed over records the authorized action's policies would have excluded, disclosing information about data the actor cannot read. The fix runs the aggregate under the same read_action it is authorized against.

This issue affects ash: from 3.5.13 before 3.32.2.

Weakness: CWE-863

Which versions are affected by CVE-2026-82748?

1 open source package ship an affected version, including ash.

PackageAffectedFixed in
ash HexFrom 3.5.133.32.2

How do I fix CVE-2026-82748?

Upgrade ash to 3.32.2 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-82748 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82748 exists.

Sources

Also known as EEF-CVE-2026-82748, GHSA-g5hp-mghm-3mgp.

Is CVE-2026-82748 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free