{"answers":{"affected":"3 open source packages ship an affected version, including litellm. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4890 exists.","fix":"No fix has been published for CVE-2024-4890 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-4890 is a medium-severity SQL injection vulnerability in berriai/litellm, published on 6 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-4890 and fix it if it is affected.\n\nWhat it is: CVE-2024-4890 is a medium-severity SQL injection vulnerability in berriai/litellm, published on 6 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4890 exists.\n\nAffected packages and fixed versions:\n- litellm (PyPI): affected all versions up to 1.27.14; no fix listed\n- litellm (PyPI): affected all versions up to 1.27.14; no fix listed\n- litellm (PyPI): affected all versions up to 1.27.14; 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-4890/ (Markdown: https://insights.sbomify.com/CVE-2024-4890/index.md)","id":"CVE-2024-4890","markdown":"https://insights.sbomify.com/CVE-2024-4890/index.md","name":"CVE-2024-4890","record":{"aliases":["GHSA-8j42-pcfm-3467","PYSEC-2026-1544"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python LLM proxy library","requires_auth":"high_privilege","summary":"An attacker can inject SQL via the user_id parameter to read sensitive database information like API keys and tokens.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"litellm","vendor":"litellm"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A blind SQL injection vulnerability exists in the berriai/litellm application, specifically within the '/team/update' process. The vulnerability arises due to the improper handling of the 'user_id' parameter in the raw SQL query used for deleting users. An attacker can exploit this vulnerability by injecting malicious SQL commands through the 'user_id' parameter, leading to potential unauthorized access to sensitive information such as API keys, user information, and tokens stored in the database. The affected version is 1.27.14.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2025-11-12","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-11-12T11:22:52Z","kind":"github_poc","ref":"https://github.com/nekr0ff/needrestart-sudo-escalate-cve-2024-4890","stars":0,"title":"PoC exploit for CVE-2024-4890: Sudo privilege escalation via neecdrestart (\u003e=3.8). Ethical lab-only. Scripts in Python and C."}],"tier":"weaponised"},"has_fix":false,"headline":"Blind SQL Injection in berriai/litellm","id":"CVE-2024-4890","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Cross-site scripting in Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks \u0026 Patterns","id":"CVE-2024-4891"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.27.14"],"package":"litellm","purl":null,"source":"GHSA-8j42-pcfm-3467"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.27.14"],"package":"litellm","purl":"pkg:pypi/litellm","source":"GHSA-8j42-pcfm-3467"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.27.14"],"package":"litellm","purl":"pkg:pypi/litellm","source":"PYSEC-2026-1544"}],"prev":{"headline":"Code Injection in berriai/litellm","id":"CVE-2024-4889"},"products":["berriai/litellm"],"published":"2024-06-06","related":[{"cvss_score":9.3,"headline":"BerriAI LiteLLM SQL Injection","id":"CVE-2026-42208","kev_date_added":"2026-05-08","published":"2026-05-08"},{"cvss_score":8.8,"headline":"BerriAI LiteLLM Improper Authentication","id":"CVE-2026-59822","kev_date_added":"2026-09-02","published":"2026-07-08"},{"cvss_score":8.7,"headline":"BerriAI LiteLLM Command Injection","id":"CVE-2026-42271","kev_date_added":"2026-06-08","published":"2026-05-08"},{"cvss_score":9.8,"headline":"Remote Code Execution in BerriAI/litellm","id":"CVE-2024-5751","kev_date_added":null,"published":"2024-06-27"},{"cvss_score":9.8,"headline":"Server-Side Template Injection in BerriAI/litellm","id":"CVE-2024-2952","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.5,"headline":"LiteLLM: Authentication Bypass via Host Header Injection","id":"CVE-2026-49468","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":9.4,"headline":"LiteLLM has an authentication bypass via OIDC userinfo cache key collision","id":"CVE-2026-35030","kev_date_added":null,"published":"2026-04-06"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["berriai"]},"summary":"An attacker can inject SQL via the user_id parameter to read sensitive database information like API keys and tokens.","url":"https://insights.sbomify.com/CVE-2024-4890/"}