AshAi sends unrecognized tool errors verbatim to MCP clients and the model, disclosing internal details
- Exploited
- No known exploitation
- Fix
- Fixed in 1.5.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.5.1.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
AshAi, the AI tooling library for Ash applications, can leak internal details such as module names and data values to a low-privileged caller who triggers a failing tool call over the network. The affected versions are from 1.5.0 up to, but not including, 1.5.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_ai allows a caller of an AshAi tool to read internal error details, including module names and data values, by making a tool call fail.
AshAi.ToToolError gained an implementation for Ash.Error.Unknown.UnknownError that returns the error's error field as is, and AshAi.Tool.Errors.format/1 sends that text to MCP clients (tool calls and resource reads in AshAi.Mcp.Server) and to the model in AshAi.ToolLoop. Ash stores the full Exception.format/2 output of a raised exception, or inspect/1 of a bare {:error, term} return, in that field. A tool result that cannot be JSON-encoded raises a Protocol.UndefinedError whose text includes the inspected value, which can be a whole record with fields the tool never returns. None of these errors were logged. The fix logs them under an error id and returns only that id to the caller.
This issue affects ash_ai: from 1.5.0 before 1.5.1.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach10/20Affects Hex packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.5.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
Evidence 5
- Advisory
- Patch
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119613
Is CVE-2026-119613 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-119613?
ash_ai (Hex): from 1.5.0 before 1.5.1. ash_ai (Hex): from 1.5.0 before 1.5.1.Source: cve.now feed data
How do I fix CVE-2026-119613?
Upgrade to a fixed version: 1.5.1.Source: cve.now feed data