Am I affected?
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.
Weaknesses & attack patterns
Weakness
CWE-863
·
Incorrect Authorization
in catalog →
MITRE ↗
Attack patterns
CAPEC-1
·
Accessing Functionality Not Properly Constrained by ACLs
MITRE ↗
Affected — Hex / ash Hex.pm ↗ Repository ↗
modules · source files · routines
Affected — GitHub / ash-project/ash Repository ↗
modules · source files · routines
References
GHSA-4259-gvr2-4xhq ↗
vendor-advisory
EEF-CVE-2026-82747 ↗
related
Credits
CVSS breakdown
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N