Am I affected?
Description
Loop with Unreachable Exit Condition (Infinite Loop) vulnerability in ash-project ash_ai allows an attacker who can influence a model's output to hang the tool loop and drive unbounded, repeated model requests.
AshAi.ToolLoop classifies a model response of :tool_calls, then filters the calls through normalize_tool_calls/2 and unprocessed_tool_calls/2. Both can empty the list: a call missing a valid name, or one reusing a tool_call_id that already has a result in history, is dropped. With an empty list the loop appended nothing and recursed with a byte-identical message list, so the conversation never advanced and the same request was re-sent every iteration. Under the supported max_iterations: :infinity this never terminated; otherwise it exhausted the full budget. Prompt-injected content can make the model re-emit a spent tool_call_id. The fix treats an empty post-filter list as terminal.
This issue affects ash_ai: from 0.6.0 before 1.0.0.
Weaknesses & attack patterns
Weakness
CWE-835
·
Loop with Unreachable Exit Condition ('Infinite Loop')
in catalog →
MITRE ↗
Attack patterns
CAPEC-130
·
Excessive Allocation
MITRE ↗
Affected — Hex / ash_ai Hex.pm ↗ Repository ↗
modules · source files · routines
Affected — GitHub / ash-project/ash_ai Repository ↗
modules · source files · routines
References
GHSA-rcx7-x2w5-mmc2 ↗
vendor-advisory
EEF-CVE-2026-82579 ↗
related
Credits
CVSS breakdown
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N