Restricted aggregate disclosure via mismatched read actions
Published Sep 1, 2026 · Updated Sep 1, 2026
Incorrect authorization in Ash 3.5.13 through 3.32.1 allows attackers to disclose restricted aggregate counts. Ash.Actions.Aggregate authorizes each group against its read_action but builds the data query with a caller-supplied action, applying different policies. Exposure requires an application to supply both actions and expose the aggregate; the result reveals counts or sums over records that the authorized action excludes.
Summary
What happened
Incorrect authorization in Ash 3.5.13 through 3.32.1 allows attackers to disclose restricted aggregate counts. Ash.Actions.Aggregate authorizes each group against its read_action but builds the data query with a caller-supplied action, applying different policies. Exposure requires an application to supply both actions and expose the aggregate; the result reveals counts or sums over records that the authorized action excludes.
The record
- CVE
- CVE-2026-82748
- Published
- Sep 1, 2026
- Updated
- Sep 1, 2026
- Vendor
- Ash Framework
- Product
- Ash
- Classifications
- CWE-863, CAPEC-1
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2026CVE publishedPublication date reported by the CVE source.
- Sep 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.5.13 <3.32.2
- Affected versionversion=d2e99980380cad610dbab3c4167e85323244bc71 <2d9b78b87d2dc72885a8aa1d660b478d42f749f7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream Ash aggregate authorization-bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo