{"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-77956 exists.","fix":"Upgrade ash_ai to 1.0.0 or later.","what":"CVE-2026-77956 is a high-severity code injection vulnerability in ash-project ash_ai, published on 31 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77956 and fix it if it is affected.\n\nWhat it is: CVE-2026-77956 is a high-severity code injection vulnerability in ash-project ash_ai, published on 31 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77956 exists.\n\nAffected packages and fixed versions:\n- ash_ai (Hex): affected from 0.1.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-77956/ (Markdown: https://insights.sbomify.com/CVE-2026-77956/index.md)","id":"CVE-2026-77956","markdown":"https://insights.sbomify.com/CVE-2026-77956/index.md","name":"CVE-2026-77956","record":{"aliases":["EEF-CVE-2026-77956","GHSA-2g59-hg7m-qc83"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir AI library","requires_auth":"none","summary":"Remote unauthenticated attackers can execute arbitrary Elixir code via EEx template injection in AshAi prompt actions.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":8.9,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Improper Control of Generation of Code (Code Injection) vulnerability in ash-project ash_ai allows a remote, unauthenticated client to execute arbitrary Elixir code.\n\nAshAi.Actions.Prompt evaluates prompt content through EEx.eval_string/2. The documented prompt: fn input, context -\u003e ... end form lets the prompt content be built from action arguments, so when a prompt action's text incorporates request data, that attacker-controlled text is compiled and run as an EEx template (Elixir source). Content such as \u003c%= System.cmd(...) %\u003e therefore executes on the server before any model request is made, requiring no authentication beyond reaching a prompt action. The fix stops evaluating function-supplied prompt content as EEx; only statically configured templates are evaluated.\n\nThis issue affects ash_ai: from 0.1.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":"EEx template evaluation of prompt content in AshAi enables remote code execution","id":"CVE-2026-77956","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Use of Hard-coded Credentials in Bransys ELD","id":"CVE-2026-77960"},"packages":[{"ecosystem":"Hex","fixed":["1.0.0"],"introduced":["0.1.0"],"last_affected":[],"package":"ash_ai","purl":"pkg:hex/ash_ai","source":"EEF-CVE-2026-77956"}],"prev":{"headline":"Possible ZONEMD verification bypass window","id":"CVE-2026-77955"},"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":"total"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["ash-project"]},"summary":"Remote unauthenticated attackers can execute arbitrary Elixir code via EEx template injection in AshAi prompt actions.","url":"https://insights.sbomify.com/CVE-2026-77956/"}