The flaw in Ash occurs when the aggregate component authorizes an operation under one read_action but executes it under another, which allows a user to request aggregate calculations that bypass the intended access controls. Because aggregates are recomputed with read policies that may be more permissive than those used for authorization, sensitive data can be revealed through sums or counts. The vulnerability is an example of an authorization bypass due to a user‑controlled key and is listed as CWE‑863.

Versions 3.5.13 through 3.32.1 of the Ash framework from ash-project are affected.

CVSS score 2.1 classifies the flaw as low severity; no EPSS score is available and it is not listed in CISA KEV. The risk is limited but could still allow an attacker who can invoke aggregates with a custom action to glean data they are not authorized to see. The likely attack vector is a remote request to an exposed API that accepts a :action parameter; no explicit local‑only vulnerabilities are described. The low score and lack of publicly available exploits suggest the immediate threat is modest, but the presence of an authorization mismatch warrants caution.