{"answers":{"affected":"3 open source packages ship an affected version, including llm.","exploited":"There is no known exploitation of CVE-2026-31236 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-31236 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-31236 is a critical code injection vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-31236 and fix it if it is affected.\n\nWhat it is: CVE-2026-31236 is a critical code injection vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-31236 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- llm (PyPI): affected all versions up to 0.27.1; no fix listed\n- llm (PyPI): affected all versions up to 0.27.1; no fix listed\n- llm (PyPI): affected all versions up to 0.27.1; no fix listed\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-31236/ (Markdown: https://insights.sbomify.com/CVE-2026-31236/index.md)","id":"CVE-2026-31236","markdown":"https://insights.sbomify.com/CVE-2026-31236/index.md","name":"CVE-2026-31236","record":{"aliases":["DEBIAN-CVE-2026-31236","GHSA-g76p-4vg5-f4qh","PYSEC-2026-400","UBUNTU-CVE-2026-31236"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"llm CLI tool","requires_auth":"none","summary":"Attackers can execute arbitrary Python code via the --functions argument in the llm CLI tool, requiring social engineering to trick victims into running malicious commands.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The llm CLI tool thru 0.27.1 contains a critical code injection vulnerability via its --functions command-line argument. This argument is intended to allow users to provide custom Python function definitions. However, the tool directly executes the provided code using the unsafe exec() function without any sanitization, sandboxing, or security restrictions. An attacker can exploit this by crafting a malicious llm command with arbitrary Python code in the --functions argument and using social engineering to trick a victim into running it. This leads to arbitrary code execution on the victim's system, potentially granting the attacker full control.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"llm CLI tool contains a code injection vulnerability via `--functions` command-line argument","id":"CVE-2026-31236","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Ludwig framework is vulnerable to insecure deserialization through its predict() method.","id":"CVE-2026-31237"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.27.1"],"package":"llm","purl":null,"source":"GHSA-g76p-4vg5-f4qh"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.27.1"],"package":"llm","purl":"pkg:pypi/llm","source":"GHSA-g76p-4vg5-f4qh"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.27.1"],"package":"llm","purl":"pkg:pypi/llm","source":"PYSEC-2026-400"}],"prev":{"headline":"imgaug contains an insecure deserialization vulnerability in BackgroundAugmenter class within multicore.py module","id":"CVE-2026-31235"},"products":["n/a"],"published":"2026-05-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["n/a"]},"summary":"Attackers can execute arbitrary Python code via the --functions argument in the llm CLI tool, requiring social engineering to trick victims into running malicious commands.","url":"https://insights.sbomify.com/CVE-2026-31236/"}