Skip to content
Connect AISign inSign up free
CVE-2026-786936.9MediumCWE-209

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

ash-project · ash_graphql

Fixed in 1.11.0 · Affected: ash-project ash_graphql before 1.11.0 · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.5%probability of exploitation in the next 30 days
44th percentile
050100

Higher than 44% of scored CVEs

6.9MediumCVSS 4.0
LowMedium

DescriptionCVE.org

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.

Affected products2

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • ash-project · ash_graphqlfrom 1.9.0 before 1.11.0
  • ash-project · ash_graphqlVersions not stated

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
August 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-78693 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References