CVE-2026-78693

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
62(Attend)
EG Risk 62/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 30, 2026

Last Modified

September 1, 2026

Advisory Details (4)

Auto-updated Aug 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit Patch Available

commit 78e90d369f09 (ash-project/ash_graphql)

Patch available: ash-project/ash_graphql v1.11.0 (contains commit 78e90d369f09)

https://github.com/ash-project/ash_graphql/commit/78e90d369f09f44c534816de541e60841066a467
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-78693
github Patch Available🟡 PoC Available

Incomplete redaction in `AshGraphql.Errors` in AshGraphql re-attaches the original error path, leaking internal field names · Advisory · ash-project/ash_graphql · GitHub

https://github.com/ash-project/ash_graphql/security/advisories/GHSA-ppr2-g9h8-w7qp

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ash_graphql1.10.0 ... 1.9.4 (7 versions)1.11.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 20:57 UTCEG score recompute
  3. 2026-09-16 22:36 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-16 00:11 UTCEG score recompute
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-14 03:30 UTCEG score recompute
  10. 2026-09-13 05:09 UTCEG score recompute
  11. 2026-09-12 06:48 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 10:05 UTCEG score recompute
  15. 2026-09-09 11:44 UTCEG score recompute
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-08 13:23 UTCEG score recompute
  18. 2026-09-06 13:59 UTCEG score recompute
  19. 2026-09-06 13:48 UTCEPSS rescore
  20. 2026-09-05 15:39 UTCEG score recompute
  21. 2026-09-04 17:17 UTCEG score recompute
  22. 2026-09-04 05:07 UTCEPSS rescore
  23. 2026-09-02 20:13 UTCEG score recompute
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 14:54 UTCEG score recompute
Show 8 more
  1. 2026-09-01 13:54 UTCEPSS rescore
  2. 2026-09-01 04:40 UTCEPSS rescore
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-08-31 16:28 UTCEG score recompute
  5. 2026-08-31 16:16 UTCEG score recompute
  6. 2026-08-30 19:28 UTCEG score recompute
  7. 2026-08-30 18:35 UTCEG score recompute
  8. 2026-08-30 18:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-78693?
CVE-2026-78693 is a medium vulnerability published on August 30, 2026. Generation of Error Message Containing Sensitive Information vulnerability in ash-project ashgraphql allows a remote client to read internal field names that an application configured its errorhandler to redact. In AshGraphql.Errors, each error is passed to the configured errorhandler and the…
When was CVE-2026-78693 disclosed?
CVE-2026-78693 was first published in the National Vulnerability Database on August 30, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78693 actively exploited?
CVE-2026-78693 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.0% of all scored CVEs.
What is the CVSS score of CVE-2026-78693?
CVE-2026-78693 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-78693?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78693, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-78693

Explore →

Is Your Infrastructure Affected by CVE-2026-78693?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.