CVE-2026-82739
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.
Scoring
- Severity
- LOW
- CVSS base score
- 2.1
- CVSS vector
- 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
- EPSS probability
- 0.13%
- CWE
- CWE-209
- Published
- 2026-09-01
- Last modified
- 2026-09-01
Affected products
- ash-project ash
- ash-project ash
Weakness type
Related vulnerabilities
- CVE-2026-66306 — Skype for Business Information Disclosure Vulnerability
- CVE-2026-69294 — Microsoft COM for Windows Information Disclosure Vulnerability
- CVE-2026-68886 — Windows Network Connection Broker Information Disclosure Vulnerability
- CVE-2026-67383 — Microsoft SQL Server Information Disclosure Vulnerability
- CVE-2026-69684 — Windows Error Reporting Information Disclosure Vulnerability
- CVE-2026-69552 — Windows Print Spooler Components Information Disclosure Vulnerability
- CVE-2026-11873 — Pki-core: dogtag-pki: empty request to dogtag /ca/rest/certrequests causes http 500, java exception, and stacktrace disclosure
- CVE-2026-82733 — Route handler return value echoed into AshTypescript error response