# CVE-2026-82739

## Summary

- **CVE ID:** CVE-2026-82739
- **Severity:** LOW
- **CVSS Score:** 2.1 (CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N)
- **CWE:** CWE-209
- **Published:** Sep 1, 2026
- **Last Modified:** Sep 1, 2026

## Description

Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash discloses the stored value of a confirmed field to an actor who fails its confirmation check.

Ash.Resource.Validation.Confirm's atomic implementation (atomic/2 in lib/ash/resource/validation/confirm.ex) built the mismatch error with its value set to the field being confirmed. When the actor supplies only the confirmation argument and not the field itself, value resolves through atomic_ref/2 to the field's current stored value, so the mismatch error echoes that stored value back to the actor. Against a confirmation guarding a sensitive attribute, an actor can submit a deliberately wrong confirmation and read the real value from the returned error. The fix reports the actor-supplied confirmation in the error instead of the stored field value.

This issue affects ash: from 2.17.20 before 3.32.2.

## Affected Products

- ash-project — ash (2.17.20)
- ash-project — ash (fadecf3ee95640bd3bc7298df4799e0375537fd2)

## References

- [CNA](https://github.com/ash-project/ash/security/advisories/GHSA-66cg-vj5m-8w7v)
- [CNA](https://cna.erlef.org/cves/CVE-2026-82739.html)
- [CNA](https://osv.dev/vulnerability/EEF-CVE-2026-82739)
- [CNA](https://github.com/ash-project/ash/commit/7dfe5f0b1ba4267580ded947dc861351d4dc8e2b)

## Exploitation Prediction (EPSS)

- **EPSS Score:** 0.13%
- **EPSS Percentile:** 2.6

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-10._