Search for packages
| purl | pkg:pypi/litellm@0.13.6.dev3 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-29vc-8g8f-zbf4
Aliases: CVE-2024-10188 GHSA-gw2q-qw9j-rgv7 |
Affected by 5 other vulnerabilities. |
|
|
VCID-362j-e9vs-73gg
Aliases: CVE-2026-35030 GHSA-jjhc-v7c2-5hh6 |
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, when JWT authentication is enabled (enable_jwt_auth: true), the OIDC userinfo cache uses token[:20] as the cache key. JWT headers produced by the same signing algorithm generate identical first 20 characters. This configuration option is not enabled by default. Most instances are not affected. An unauthenticated attacker can craft a token whose first 20 characters match a legitimate user's cached token. On cache hit, the attacker inherits the legitimate user's identity and permissions. This affects deployments with JWT/OIDC authentication enabled. Fixed in v1.83.0. |
Affected by 4 other vulnerabilities. |
|
VCID-58cv-nn1s-qqdx
Aliases: CVE-2024-4264 GHSA-7ggm-4rjg-594w |
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`. |
Affected by 14 other vulnerabilities. |
|
VCID-9euc-j2j6-7ba3
Aliases: CVE-2024-4888 GHSA-3xr8-qfvj-9p9j |
BerriAI's litellm, in its latest version, is vulnerable to arbitrary file deletion due to improper input validation on the `/audio/transcriptions` endpoint. An attacker can exploit this vulnerability by sending a specially crafted request that includes a file path to the server, which then deletes the specified file without proper authorization or validation. This vulnerability is present in the code where `os.remove(file.filename)` is used to delete a file, allowing any user to delete critical files on the server such as SSH keys, SQLite databases, or configuration files. |
Affected by 12 other vulnerabilities. |
|
VCID-ddyq-1w9w-6bg6
Aliases: CVE-2024-5710 GHSA-qqcv-vg9f-5rr3 |
berriai/litellm version 1.34.34 is vulnerable to improper access control in its team management functionality. This vulnerability allows attackers to perform unauthorized actions such as creating, updating, viewing, deleting, blocking, and unblocking any teams, as well as adding or deleting any member to or from any teams. The vulnerability stems from insufficient access control checks in various team management endpoints, enabling attackers to exploit these functionalities without proper authorization. |
Affected by 11 other vulnerabilities. |
|
VCID-dzdw-y87c-9fh7
Aliases: CVE-2024-2952 GHSA-46cm-pfwv-cgf8 |
BerriAI/litellm is vulnerable to Server-Side Template Injection (SSTI) via the `/completions` endpoint. The vulnerability arises from the `hf_chat_template` method processing the `chat_template` parameter from the `tokenizer_config.json` file through the Jinja template engine without proper sanitization. Attackers can exploit this by crafting malicious `tokenizer_config.json` files that execute arbitrary code on the server. |
Affected by 13 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-efwj-d5hx-kye8
Aliases: CVE-2025-0628 GHSA-fjcf-3j3r-78rp |
An improper authorization vulnerability exists in the main-latest version of BerriAI/litellm. When a user with the role 'internal_user_viewer' logs into the application, they are provided with an overly privileged API key. This key can be used to access all the admin functionality of the application, including endpoints such as '/users/list' and '/users/get_users'. This vulnerability allows for privilege escalation within the application, enabling any account to become a PROXY ADMIN. |
Affected by 3 other vulnerabilities. |
|
VCID-j4xv-tkgp-q7em
Aliases: CVE-2024-9606 GHSA-g5pg-73fc-hjwq |
Affected by 7 other vulnerabilities. |
|
|
VCID-jw3v-fdn2-bugj
Aliases: CVE-2026-35029 GHSA-53mr-6c8q-9789 |
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, the /config/update endpoint does not enforce admin role authorization. A user who is already authenticated into the platform can then use this endpoint to modify proxy configuration and environment variables, register custom pass-through endpoint handlers pointing to attacker-controlled Python code, achieving remote code execution, read arbitrary server files by setting UI_LOGO_PATH and fetching via /get_image, and take over other privileged accounts by overwriting UI_USERNAME and UI_PASSWORD environment variables. Fixed in v1.83.0. |
Affected by 4 other vulnerabilities. |
|
VCID-k2fv-6edv-q3gr
Aliases: CVE-2024-5751 GHSA-gppg-gqw8-wh9g |
BerriAI/litellm version v1.35.8 contains a vulnerability where an attacker can achieve remote code execution. The vulnerability exists in the `add_deployment` function, which decodes and decrypts environment variables from base64 and assigns them to `os.environ`. An attacker can exploit this by sending a malicious payload to the `/config/update` endpoint, which is then processed and executed by the server when the `get_secret` function is triggered. This requires the server to use Google KMS and a database to store a model. |
Affected by 10 other vulnerabilities. |
|
VCID-kqcb-nxq1-abdq
Aliases: CVE-2024-4890 GHSA-8j42-pcfm-3467 |
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. |
Affected by 15 other vulnerabilities. |
|
VCID-mnn6-ght8-5bg1
Aliases: CVE-2024-6587 GHSA-g26j-5385-hhw3 |
A Server-Side Request Forgery (SSRF) vulnerability exists in berriai/litellm version 1.38.10. This vulnerability allows users to specify the `api_base` parameter when making requests to `POST /chat/completions`, causing the application to send the request to the domain specified by `api_base`. This request includes the OpenAI API key. A malicious user can set the `api_base` to their own domain and intercept the OpenAI API key, leading to unauthorized access and potential misuse of the API key. |
Affected by 8 other vulnerabilities. |
|
VCID-s1sj-yr6f-afdc
Aliases: CVE-2025-0330 GHSA-879v-fggm-vxw2 |
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. |
Affected by 6 other vulnerabilities. |
|
VCID-tssn-kdqp-jbez
Aliases: GHSA-69x8-hrgq-fjj8 |
LiteLLM: Password hash exposure and pass-the-hash authentication bypass ### Impact Three issues combine into a full authentication bypass chain: 1. Weak hashing: User passwords are stored as unsalted SHA-256 hashes, making them vulnerable to rainbow table attacks and trivially identifying users with identical passwords. 2. Hash exposure: Multiple API endpoints (/user/info, /user/update, /spend/users) return the password hash field in responses to any authenticated user regardless of role. Plaintext passwords could also potentially be exposed in certain scenarios. 4. Pass-the-hash: The /v2/login endpoint accepts the raw SHA-256 hash as a valid password without re-hashing, allowing direct login with a stolen An already authenticated user can retrieve another user's password hash from the API and use it to log in as that user. This enables full privilege escalation in three HTTP requests. ### Patches Fixed in v1.83.0. Passwords are now hashed with scrypt (random 16-byte salt, n=16384, r=8, p=1). Password hashes are stripped from all API responses. Existing SHA-256 hashes are transparently migrated on next login. |
Affected by 4 other vulnerabilities. |
|
VCID-vc9h-2h9t-v3bs
Aliases: CVE-2024-8984 GHSA-fh2c-86xm-pm2x |
A Denial of Service (DoS) vulnerability exists in berriai/litellm version v1.44.5. This vulnerability can be exploited by appending characters, such as dashes (-), to the end of a multipart boundary in an HTTP request. The server continuously processes each character, leading to excessive resource consumption and rendering the service unavailable. The issue is unauthenticated and does not require any user interaction, impacting all users of the service. |
Affected by 4 other vulnerabilities. |
|
VCID-vgkp-n2vv-k7c9
Aliases: CVE-2024-5225 GHSA-h6m6-jj8v-94jj |
An SQL Injection vulnerability exists in the berriai/litellm repository, specifically within the `/global/spend/logs` endpoint. The vulnerability arises due to improper neutralization of special elements used in an SQL command. The affected code constructs an SQL query by concatenating an unvalidated `api_key` parameter directly into the query, making it susceptible to SQL Injection if the `api_key` contains malicious data. This issue affects the latest version of the repository. Successful exploitation of this vulnerability could lead to unauthorized access, data manipulation, exposure of confidential information, and denial of service (DoS). |
Affected by 11 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||