CVE-2026-82747
Incorrect Authorization vulnerability in ash-project ash returns …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- cna.erlef.org/cves/CVE-2026-82747.html
- github.com/ash-project/ash/commit/6eddb8ab26e45023faf0c79ebd152bb40aefda02
- github.com/ash-project/ash/security/advisories/GHSA-4259-gvr2-4xhq
- osv.dev/vulnerability/EEF-CVE-2026-82747
- github.com/ash-project/ash/commit/f4a8ff53fd3b974468d73685cd3fc842ef893de3
- nvd.nist.gov/vuln/detail/CVE-2026-82747
- cve.org/CVERecord?id=CVE-2026-82747
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.