Ash.Reactor change step fails open, skipping a change when its where guard raises (CVE-2026-82744) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-82744

Ash.Reactor change step fails open, skipping a change when its where guard raises

Answer in brief

CVE-2026-82744 records a Unknown severity 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). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 1, 2026Updated Sep 1, 2026Source checked Sep 1, 2026First seen by HOL Sep 1, 2026Material review Sep 1, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps ash-project/ash (generic), ash-project/ash (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ash-project/ashgeneric	>=3.0.0-rc.17 <3.32.2	3.32.2
ash-project/ashgeneric	>=321f43bd05ad9544e693cbf797243693e51a6be4 <6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc	6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc

Recommended response

Check inventory. Check lockfiles and deployed manifests for ash-project/ash, ash-project/ash.
Review the reported fix. Update ash-project/ash to 3.32.2; ash-project/ash to 6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 1, 2026

Sources and claim methodology

Upstream source description

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.