{"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-2025-0330 exists.","fix":"No fix has been published for CVE-2025-0330 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0330 is a high-severity vulnerability in berriai/litellm, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-0330 and fix it if it is affected.\n\nWhat it is: CVE-2025-0330 is a high-severity vulnerability in berriai/litellm, published on 20 Mar 2025. 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-2025-0330 exists.\n\nAffected packages and fixed versions:\n- litellm (PyPI): affected all versions up to 1.52.1; no fix listed\n- litellm (PyPI): affected all versions up to 1.52.1; no fix listed\n- litellm (PyPI): affected all versions up to 1.52.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-2025-0330/ (Markdown: https://insights.sbomify.com/CVE-2025-0330/index.md)","id":"CVE-2025-0330","markdown":"https://insights.sbomify.com/CVE-2025-0330/index.md","name":"CVE-2025-0330","record":{"aliases":["GHSA-879v-fggm-vxw2","PYSEC-2026-1543"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LiteLLM proxy library","requires_auth":"none","summary":"Attackers can obtain Langfuse API keys via error messages, granting full access to stored request data in LiteLLM deployments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"litellm","vendor":"litellm"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-1230","name":"Exposure of Sensitive Information Through Metadata"}],"description":"In berriai/litellm version v1.52.1, an issue in proxy_server.py causes the leakage of Langfuse API keys when an error occurs while parsing team settings. This vulnerability exposes sensitive information, including langfuse_secret and langfuse_public_key, which can provide full access to the Langfuse project storing all requests.","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":"Exposure of Sensitive Information in berriai/litellm","id":"CVE-2025-0330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"YunzMall HTTP POST Request ResetpwdController.php changePwd password recovery","id":"CVE-2025-0331"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.52.1"],"package":"litellm","purl":null,"source":"GHSA-879v-fggm-vxw2"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.52.1"],"package":"litellm","purl":"pkg:pypi/litellm","source":"GHSA-879v-fggm-vxw2"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.52.1"],"package":"litellm","purl":"pkg:pypi/litellm","source":"PYSEC-2026-1543"}],"prev":{"headline":"AI ChatBot for WordPress – WPBot \u003c 6.2.4 - Admin+ Stored XSS","id":"CVE-2025-0329"},"products":["berriai/litellm"],"published":"2025-03-20","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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["berriai"]},"summary":"Attackers can obtain Langfuse API keys via error messages, granting full access to stored request data in LiteLLM deployments.","url":"https://insights.sbomify.com/CVE-2025-0330/"}