Ash.Reactor change step fails open, skipping a change when its where guard raises
ash-project ash
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ash-project ash |
| No fix yet |
| ash-project ash |
| No fix yet |
Original 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.
From the CVE record · EEF
References
- github.com/ash-project/ash/security/advisories/GHSA-3xq4-m876-fr88Exploit
- cna.erlef.org/cves/CVE-2026-82744.html
- osv.dev/vulnerability/EEF-CVE-2026-82744
- github.com/ash-project/ash/commit/6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabcPatch
- github.com
- repo.hex.pm
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/82xxx/CVE-2026-82744.json
- nvd.nist.gov/vuln/detail/CVE-2026-82744
- github.com/ash-project/ash