{"answers":{"affected":"1 open source package ship an affected version, including ash_ai.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82580 exists.","fix":"Upgrade ash_ai to 1.0.0 or later.","what":"CVE-2026-82580 is a medium-severity vulnerability in ash-project ash_ai, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82580 and fix it if it is affected.\n\nWhat it is: CVE-2026-82580 is a medium-severity vulnerability in ash-project ash_ai, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82580 exists.\n\nAffected packages and fixed versions:\n- ash_ai (Hex): affected from 0.6.0; fixed in 1.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82580/ (Markdown: https://insights.sbomify.com/CVE-2026-82580/index.md)","id":"CVE-2026-82580","markdown":"https://insights.sbomify.com/CVE-2026-82580/index.md","name":"CVE-2026-82580","record":{"aliases":["EEF-CVE-2026-82580","GHSA-5747-6mpw-6m9c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir AI library","requires_auth":"low_privilege","summary":"Attackers can trigger tool exceptions to leak sensitive internal error details, such as database constraints or query fragments, to chat users.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_ai discloses internal error text to chat users.\n\nIn 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.\n\nThis issue affects ash_ai: from 0.6.0 before 1.0.0.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"AshAi echoes raw tool exception messages into the conversation, disclosing internal details","id":"CVE-2026-82580","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Missing authorization in SHIRASAGI","id":"CVE-2026-82582"},"packages":[{"ecosystem":"Hex","fixed":["1.0.0"],"introduced":["0.6.0"],"last_affected":[],"package":"ash_ai","purl":"pkg:hex/ash_ai","source":"EEF-CVE-2026-82580"}],"prev":{"headline":"AshAi tool loop never terminates when all tool calls are filtered out, enabling denial of service","id":"CVE-2026-82579"},"products":["ash_ai"],"published":"2026-08-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["ash-project"]},"summary":"Attackers can trigger tool exceptions to leak sensitive internal error details, such as database constraints or query fragments, to chat users.","url":"https://insights.sbomify.com/CVE-2026-82580/"}