CVE-2026-82744 Ash.Reactor change step fails open, skipping a change when its where guard raises
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
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.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| ash-project ash | >= 3.0.0-rc.17, < 3.32.2; >= 321f43bd05ad9544e693cbf797243693e51a6be4, < 6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc | 3.32.2, 6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| ash-project ash | >= 3.0.0-rc.17, < 3.32.2 | 3.32.2 |
| ash-project ash | >= 321f43bd05ad9544e693cbf797243693e51a6be4, < 6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc | 6d2eb86ea8d2ba5ffac89c1b8b9bf46e331feabc |
References
- github.com exploit related vendor-advisory
- EEF CNA record for CVE-2026-82744 related
- OSV record EEF-CVE-2026-82744 related
- Fix commit 6d2eb86 in ash-project/ash patch
- Introducing commit 321f43b in ash-project/ash related
- ENISA EUVD EUVD-2026-68949 third-party-advisory