CVE-2026-82580

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: 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_ai discloses internal error text to chat users.

In AshAi.ToolLoop and AshAi.Tools, an exception raised while executing a tool was serialized verbatim with Exception.message/1 into the tool-result content. That content is appended to the conversation, emitted as a {:tool_result, ...} stream event, and sent back to the model, which typically relays it to the user. No filtering happened first, so anything raised inside a tool callback or lifecycle hook (database constraint messages, adapter errors, query fragments, policy or validation internals) was echoed as-is. A chat user who can steer tool arguments into a raising code path receives the raw internal text. The fix routes raised tool errors through the same safe formatter used for other tool errors.

This issue affects ash_ai: from 0.6.0 before 1.0.0.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

August 31, 2026

Last Modified

September 1, 2026

Advisory Details (4)

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

commit c68dfbdb2204 (ash-project/ash_ai)

Patch available: ash-project/ash_ai v1.0.0 (contains commit c68dfbdb2204)

https://github.com/ash-project/ash_ai/commit/c68dfbdb220426dc015b58379e95bde8e9f0995a
generic

OSV - Open Source Vulnerabilities

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

Information disclosure in `AshAi.ToolLoop` in AshAi echoes raw exception messages into the conversation · Advisory · ash-project/ash_ai · GitHub

https://github.com/ash-project/ash_ai/security/advisories/GHSA-5747-6mpw-6m9c

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ash_ai0.6.0 ... 0.8.2 (9 versions)1.0.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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-01 16:37 UTCEG score recompute
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-31 16:25 UTCEG score recompute
  6. 2026-08-31 16:15 UTCEG score recompute
  7. 2026-08-31 02:26 UTCEG score recompute
  8. 2026-08-31 01:34 UTCEG score recompute
  9. 2026-08-31 01:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82580?
CVE-2026-82580 is a medium vulnerability published on August 31, 2026. Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_ai discloses internal error text to chat users. In AshAi.ToolLoop and AshAi.Tools, an exception raised while executing a tool was serialized verbatim with Exception.message/1 into the tool-result content.…
When was CVE-2026-82580 disclosed?
CVE-2026-82580 was first published in the National Vulnerability Database on August 31, 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-82580 actively exploited?
CVE-2026-82580 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 81.4% of all scored CVEs.
What is the CVSS score of CVE-2026-82580?
CVE-2026-82580 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-82580?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82580, 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-82580

Explore →

Is Your Infrastructure Affected by CVE-2026-82580?

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