Vulnerability Description
Incorrect Authorization vulnerability in ash-project ash returns records that a runtime read policy denies to any actor. When a resource has an access_type :runtime read policy (a check evaluated per record rather than compiled to a filter), Ash.Policy.Authorizer decides each record in check_result/1 (lib/ash/policy/authorizer/authorizer.ex) by discarding impossible policy scenarios and inspecting what remains. When every scenario for a record was impossible, meaning no policy can authorize it and it must be forbidden, the empty-scenario branch instead kept the record ({[record | data], authorizer, any_forbidden?}) and returned it as authorized. As a result, records the runtime read policy denies are returned to any actor. The fix forbids a record whose scenarios are all impossible. This issue affects ash: from 3.4.44 before 3.32.2.
Related Weaknesses (CWE)
References
- https://cna.erlef.org/cves/CVE-2026-82747.html
- https://github.com/ash-project/ash/commit/6eddb8ab26e45023faf0c79ebd152bb40aefda
- https://github.com/ash-project/ash/security/advisories/GHSA-4259-gvr2-4xhq
- https://osv.dev/vulnerability/EEF-CVE-2026-82747
- https://github.com/ash-project/ash/security/advisories/GHSA-4259-gvr2-4xhq
FAQ
What is CVE-2026-82747?
CVE-2026-82747 is a documented vulnerability. Incorrect Authorization vulnerability in ash-project ash returns records that a runtime read policy denies to any actor. When a resource has an access_type :runtime read policy (a check evaluated per...
How severe is CVE-2026-82747?
CVSS scoring is not yet available for CVE-2026-82747. Check NVD for updates.
Is there a patch for CVE-2026-82747?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.