{"id":"CVE-2026-101028","title":"Incorrect Authorization vulnerability in ash-project ash allows an actor to infer data in related records they cannot read via Ash.count/2, Ash.exists/2 and Ash.aggregate/3.\n\nAsh.Actions.Aggregate.run/4 (lib/ash/actions/aggregate.ex) app…","summary":"Incorrect Authorization vulnerability in ash-project ash allows an actor to infer data in related records they cannot read via Ash.count/2, Ash.exists/2 and Ash.aggregate/3.\n\nAsh.Actions.Aggregate.run/4 (lib/ash/actions/aggregate.ex) app…","severity":"medium","cwe":["CWE-863"],"published":"2026-10-09","updated":"2026-10-09","sourceUpdated":"2026-10-09T07:17:17.627","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-101028","references":[{"url":"https://cna.erlef.org/cves/CVE-2026-101028.html","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"},{"url":"https://github.com/ash-project/ash/commit/30eaf1c6e8524527b703e3c4bfeff7967ee0b37c","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"},{"url":"https://github.com/ash-project/ash/commit/80936187b27ee94f15cd875affd3141b5cb23185","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"},{"url":"https://github.com/ash-project/ash/security/advisories/GHSA-xj24-8f5c-pp5p","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"},{"url":"https://osv.dev/vulnerability/EEF-CVE-2026-101028","label":"6b3ad84c-e1a6-4bf7-a703-f496b71e49db"},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-101028.json"},{"url":"https://access.redhat.com/security/cve/CVE-2026-101028"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-101028"}],"tags":["nvd","csaf","vex","red-hat"],"ingestedAt":"2026-10-09T07:28:22.264Z","vendor":"Red Hat","cvss":6.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","cvssSource":"vendor","slug":"CVE-2026-101028","body":"## Overview\n\nIncorrect Authorization vulnerability in ash-project ash allows an actor to infer data in related records they cannot read via Ash.count/2, Ash.exists/2 and Ash.aggregate/3.\n\nAsh.Actions.Aggregate.run/4 (lib/ash/actions/aggregate.ex) applied only the root resource's read policy before running the aggregate query. The read path also applies each related resource's read policy to filter and sort references that cross a relationship, directly (for example comments.body) or through an aggregate over one, but the aggregate path skipped that step. A caller whose filter or sort reaches these functions, for example through Ash.Query.filter_input/2, an ash_lua script, or an AshAi tool offering count or exists results, can test conditions against related rows hidden from them and recover their existence and attribute values one query at a time. Ash.read/2 and its page counts are not affected.\n\nThis issue affects ash: from 2.6.0 before 3.34.6.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n## Vendor advisories\n\n- **Red Hat VEX** · updated 2026-10-09 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-101028.json)","depth":"sunlit","depthScore":36,"depthScoreParts":{"impact":35.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[{"seq":218416,"id":"CVE-2026-101028","ts":1791533717517,"field":"cvss","old":null,"new":"6.5"},{"seq":218415,"id":"CVE-2026-101028","ts":1791533717517,"field":"severity","old":"none","new":"medium"}]}