Quick answers
- Is CVE-2026-82579 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82579 being exploited in the wild.
- How severe is CVE-2026-82579?
- Informational severity, published 31 August 2026.
- Which products and versions are affected?
- Ash-Project Ash Ai 0.6.0 before 1.0.0.
- Is there a fix for CVE-2026-82579?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82579 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82579?
- 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.
Technical details
The vulnerability is an infinite loop caused by unreachable exit conditions in the AshAi.ToolLoop component. When normalize_tool_calls/2 and unprocessed_tool_calls/2 filter tool calls from a model response, they can produce an empty list if calls lack valid names or reuse spent tool_call_ids already in history. A byte-identical message list is recursed with without advancement, and the same request is re-sent every iteration. Under max_iterations: :infinity, this never terminates. Prompt-injected content can manipulate the model to re-emit spent tool_call_ids, triggering the flaw. The fix treats an empty post-filter list as terminal, breaking the loop. Attack requires ability to influence model output, such as through adversarial prompts or injected context.
Affected products
- ash-project ash_ai 0.6.0 before 1.0.0
Timeline
- 2026-08-31: disclosed