Answer in brief
CVE-2026-82744 records a Low severity (CVSS 2.1) vulnerability in Ash.Reactor change step fails open, skipping a change when its where guard raises. 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 2.1. 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 | >=321f43bd05ad9544e693cbf797243693e51a6be4 <6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc | 6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc |
| ash-project/ashgeneric | >=3.0.0-rc.17 <3.32.2 | 3.32.2 |
| ash-project/ash-project/ashgeneric | >=321f43bd05ad9544e693cbf797243693e51a6be4 <6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc | 6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc |
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
Not Failing Securely (Failing Open) vulnerability in ash-project ash skips an Ash.Reactor change when the guard controlling it raises, so a change meant to run does not. An Ash.Reactor change step can be gated by where validations that decide whether the change runs. Ash.Reactor.ChangeStep (lib/ash/reactor/steps/change_step.ex) evaluated those guards in apply_where_clauses/3, and apply_validation rescued any exception into {:error, error}. The reduce treated that identically to a guard whose condition was simply not met and bypassed the change. So when a guard raises (for example on attacker-influenced input), a change that enforces a security-relevant modification is skipped rather than failing the step. The fix distinguishes a raised exception (now {:raised, error}) and halts the step with an error, failing closed. This issue affects ash: from 3.0.0-rc.17 before 3.32.2.
Quoted source text, attributed separately from HOL analysis.