{"answers":{"affected":"3 open source packages ship an affected version, including litellm.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4264 exists.","fix":"No fix has been published for CVE-2024-4264 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-4264 is a critical code injection vulnerability in berriai/litellm, published on 18 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-4264 and fix it if it is affected.\n\nWhat it is: CVE-2024-4264 is a critical code injection vulnerability in berriai/litellm, published on 18 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4264 exists.\n\nAffected packages and fixed versions:\n- litellm (PyPI): affected all versions up to 1.28.11; no fix listed\n- litellm (PyPI): affected all versions up to 1.28.11; no fix listed\n- litellm (PyPI): affected all versions up to 1.28.11; 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-2024-4264/ (Markdown: https://insights.sbomify.com/CVE-2024-4264/index.md)","id":"CVE-2024-4264","markdown":"https://insights.sbomify.com/CVE-2024-4264/index.md","name":"CVE-2024-4264","record":{"aliases":["GHSA-7ggm-4rjg-594w","PYSEC-2026-1542"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Python LLM proxy library","requires_auth":"none","summary":"Attackers can execute arbitrary code by injecting malicious values into environment variables via the config update endpoint when Google KMS is used.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"A remote code execution (RCE) vulnerability exists in the berriai/litellm project due to improper control of the generation of code when using the `eval` function unsafely in the `litellm.get_secret()` method. Specifically, when the server utilizes Google KMS, untrusted data is passed to the `eval` function without any sanitization. Attackers can exploit this vulnerability by injecting malicious values into environment variables through the `/config/update` endpoint, which allows for the update of settings in `proxy_server_config.yaml`.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Remote Code Execution in berriai/litellm","id":"CVE-2024-4264","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Cross-site scripting in Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder \u0026 Template Kits","id":"CVE-2024-4265"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.28.11"],"package":"litellm","purl":null,"source":"GHSA-7ggm-4rjg-594w"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.28.11"],"package":"litellm","purl":"pkg:pypi/litellm","source":"GHSA-7ggm-4rjg-594w"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.28.11"],"package":"litellm","purl":"pkg:pypi/litellm","source":"PYSEC-2026-1542"}],"prev":{"headline":"Improper Access Control in mlflow/mlflow","id":"CVE-2024-4263"},"products":["berriai/litellm"],"published":"2024-05-18","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-03","vendors":["berriai"]},"summary":"Attackers can execute arbitrary code by injecting malicious values into environment variables via the config update endpoint when Google KMS is used.","url":"https://insights.sbomify.com/CVE-2024-4264/"}