Quick answers
- Is CVE-2026-119613 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119613 being exploited in the wild.
- How severe is CVE-2026-119613?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Ash-Project Ash Ai 1.5.0.
- Is there a fix for CVE-2026-119613?
- Yes: fixed in ash_ai 1.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119613 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119613?
- Check whether you run Ash-Project Ash Ai at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: ash_ai 1.5.1
Technical details
A handler for Ash.Error.Unknown.UnknownError in AshAi.ToToolError returns the full error field without sanitization, which contains Exception.format/2 output or inspect/1 of exceptions. This error text is sent to MCP clients and language models without filtering. Additionally, tool results that fail JSON encoding raise Protocol.UndefinedError with inspected values of complete records. The fix logs these errors with an error ID and returns only the ID to callers, preventing information leakage.
Affected products
- ash-project ash_ai 1.5.0
Timeline
- 2026-11-09: disclosed