CVE-2026-82739

Published: Set 01, 2026 Last Modified: Set 01, 2026
ExploitDB:
Other exploit source:
Google Dorks:
LOW 2,1
Source: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
Attack Vector: local
Attack Complexity: low
Privileges Required: none
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation Available

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.

209

Generation of Error Message Containing Sensitive Information

Draft
Common Consequences
Security Scopes Affected:
Confidentiality
Potential Impacts:
Read Application Data
Applicable Platforms
Languages: PHP, Java, Not Language-Specific
View CWE Details
https://cna.erlef.org/cves/CVE-2026-82739.html
https://github.com/ash-project/ash/commit/7dfe5f0b1ba4267580ded947dc861351d4dc8…
https://github.com/ash-project/ash/security/advisories/GHSA-66cg-vj5m-8w7v
https://osv.dev/vulnerability/EEF-CVE-2026-82739