Answer in brief
CVE-2026-82747 records a Medium severity (CVSS 5.9) vulnerability in Ash.Policy.Authorizer returns records denied by a runtime read policy to any actor. The current sources do not mark it as known exploited. The current feed maps ash-project/ash (generic), ash-project/ash (generic), ash-project/ash-project/ash (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ash-project/ash (generic), ash-project/ash (generic), ash-project/ash-project/ash (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ashgeneric | >=f4a8ff53fd3b974468d73685cd3fc842ef893de3 <6eddb8ab26e45023faf0c79ebd152bb40aefda02 | 6eddb8ab26e45023faf0c79ebd152bb40aefda02 |
| ash-project/ashgeneric | >=3.4.44 <3.32.2 | 3.32.2 |
| ash-project/ash-project/ashgeneric | >=f4a8ff53fd3b974468d73685cd3fc842ef893de3 <6eddb8ab26e45023faf0c79ebd152bb40aefda02 | 6eddb8ab26e45023faf0c79ebd152bb40aefda02 |
Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.