Answer in brief
CVE-2026-82739 records a Low severity (CVSS 2.1) vulnerability in Ash.Resource.Validation.Confirm leaks a confirmed field's stored value in the atomic mismatch error. The current sources do not mark it as known exploited. The current feed maps ash-project/ash (generic), ash-project/ash (generic), ash-project/ash-project/ash (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 2.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ash-project/ash (generic), ash-project/ash (generic), ash-project/ash-project/ash (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ashgeneric | >=fadecf3ee95640bd3bc7298df4799e0375537fd2 <7dfe5f0b1ba4267580ded947dc861351d4dc8e2b | 7dfe5f0b1ba4267580ded947dc861351d4dc8e2b |
| ash-project/ashgeneric | >=2.17.20 <3.32.2 | 3.32.2 |
| ash-project/ash-project/ashgeneric | >=fadecf3ee95640bd3bc7298df4799e0375537fd2 <7dfe5f0b1ba4267580ded947dc861351d4dc8e2b | 7dfe5f0b1ba4267580ded947dc861351d4dc8e2b |
Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.