Incomplete redaction re-attaches the original error path in AshGraphql, leaking internal field names (CVE-2026-78693) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-78693

Incomplete redaction re-attaches the original error path in AshGraphql, leaking internal field names

Answer in brief

CVE-2026-78693 records a Unknown severity vulnerability in Incomplete redaction re-attaches the original error path in AshGraphql, leaking internal field names. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_graphql (generic), ash-project/ash_graphql (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 30, 2026Updated Aug 30, 2026Source checked Aug 30, 2026First seen by HOL Aug 30, 2026Material review Aug 30, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps ash-project/ash_graphql (generic), ash-project/ash_graphql (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ash-project/ash_graphqlgeneric	>=1.9.0 <1.11.0	1.11.0
ash-project/ash_graphqlgeneric	>=6d2d8d995906d68cc245d209a9b3f9853405eb61 <78e90d369f09f44c534816de541e60841066a467	78e90d369f09f44c534816de541e60841066a467

Recommended response

Check inventory. Check lockfiles and deployed manifests for ash-project/ash_graphql, ash-project/ash_graphql.
Review the reported fix. Update ash-project/ash_graphql to 1.11.0; ash-project/ash_graphql to 78e90d369f09f44c534816de541e60841066a467 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 30, 2026

Sources and claim methodology

Upstream source description

Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_graphql allows a remote client to read internal field names that an application configured its error_handler to redact. In AshGraphql.Errors, each error is passed to the configured error_handler and the returned map is merged with the pre-handler path via Map.put_new(handled, :path, path). Because put_new defers to the handler only when the handler itself set :path, a sanitizing handler that returns a fresh map or deletes :path has that decision reverted. The re-injected path comes from build_error_path/5, which falls back to raw internal Ash attribute and argument names when no field_names mapping is configured. A validation failure on a non-exposed or nested field therefore returns internal names in the GraphQL error path, defeating the application's redaction. This issue affects ash_graphql: from 1.9.0 before 1.11.0.

Quoted source text, attributed separately from HOL analysis.