litellm 1.100.4

Direct Vulnerabilities

Known vulnerabilities in the litellm package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
H Authorization Bypass Through User-Controlled Key litellm is a Library to easily interface with LLM API providers Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key in the `add_new_model` and `can_user_make_team_model_call` functions in `model_management_endpoints.py`, which authorize the caller by role alone and never inspect the values supplied in `litellm_params`. A user with team administrator access can read any environment variable of the proxy process, including the proxy master key, by registering a model whose `api_key` is an `os.environ/<NAME>` reference and whose `api_base` points to a host they control, then invoking it so that `get_secret` resolves the variable and `_resolve_db_litellm_param` sends it to that host as the outbound `Authorization` header. This requires `STORE_MODEL_IN_DB` to be enabled and an enterprise license, which is what makes the team administrator role available. Note: A fix is unlikely. In https://github.com/BerriAI/litellm/commit/5862be3e79154ce5ac8a736c77c7c3614fac40fb, project maintainers removed the field whitelist and the team-scope short-circuit in `_resolve_db_litellm_param` deliberately, describing universal `os.environ/` resolution for team-scoped rows as an intended threat-model expansion that trusts team administrators to read environment variables, and placing the trust boundary on who the deployment grants team administrator rather than on what those administrators may reference. How to fix Authorization Bypass Through User-Controlled Key? There is no fixed version for `litellm`.	[1.93.0.dev2,)
H Weak Authentication litellm is a Library to easily interface with LLM API providers Affected versions of this package are vulnerable to Weak Authentication via the JWT authentication flow's email-based fallback lookup, which does not verify the `email_verified` claim before resolving a user identity. An attacker holding a valid JWT from the configured identity provider can present a token containing an unverified email address that matches a victim's account, causing the system to authenticate the attacker as that victim and inherit their role, including `proxy_admin` privileges. This also permanently overwrites the victim's stored identity binding, granting the attacker persistent unauthorized access to administrative endpoints that expose API keys and user management functions. How to fix Weak Authentication? There is no fixed version for `litellm`.	[0,)
H Incorrect Authorization litellm is a Library to easily interface with LLM API providers Affected versions of this package are vulnerable to Incorrect Authorization via a tenant isolation bypass vulnerability in the semantic cache layer that allows authenticated users to read other tenants' cached responses by exploiting a metadata key mismatch between _get_semantic_cache_tenant_scope() and _get_metadata_variable_name(). Attackers holding a valid virtual key can submit semantically similar prompts on affected routes such as /v1/responses and /bedrock/* to retrieve cached responses containing other tenants' personally identifiable information, financial data, or source code, and can cause agentic front-ends to auto-execute attacker-supplied tool calls under victim credentials by returning cached function_call or tool_calls payloads to a different principal. How to fix Incorrect Authorization? Upgrade `litellm` to version 1.101.0rc1 or higher.	[,1.101.0rc1)
M Insufficient Session Expiration litellm is a Library to easily interface with LLM API providers Affected versions of this package are vulnerable to Insufficient Session Expiration in the `get_redirect_response_from_openid()` function of the SSO Authentication Flow process. An attacker can cause premature session termination by manipulating authentication responses remotely, potentially leading to unauthorized session expiration and disruption of user access. How to fix Insufficient Session Expiration? There is no fixed version for `litellm`.	[0,)
M Missing Authentication for Critical Function litellm is a Library to easily interface with LLM API providers Affected versions of this package are vulnerable to Missing Authentication for Critical Function in the `/sso/debug/login` and `/sso/debug/callback` endpoints in the SSO Debug Flow. An attacker can gain unauthorized access and potentially manipulate sensitive information by sending crafted requests to the affected endpoint. How to fix Missing Authentication for Critical Function? There is no fixed version for `litellm`.	[0,)
L Incorrect Authorization litellm is a Library to easily interface with LLM API providers Affected versions of this package are vulnerable to Incorrect Authorization in the `user_api_key_auth.py` file of the M2M JWT Handler. An attacker can gain unauthorized access to resources by exploiting insufficient authorization checks. Note: This is only exploitable if the attacker possesses valid but limited credentials and can craft specific JWTs to bypass intended access controls. How to fix Incorrect Authorization? There is no fixed version for `litellm`.	[0,)
H Insufficient Session Expiration litellm is a Library to easily interface with LLM API providers Affected versions of this package are vulnerable to Insufficient Session Expiration in the `authenticate_user` function. An attacker can gain unauthorized access or maintain access to sensitive information by exploiting session management flaws. How to fix Insufficient Session Expiration? There is no fixed version for `litellm`.	[0,)

Vulnerability

Vulnerable Version

Authorization Bypass Through User-Controlled Key

litellm is a Library to easily interface with LLM API providers

Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key in the add_new_model and can_user_make_team_model_call functions in model_management_endpoints.py, which authorize the caller by role alone and never inspect the values supplied in litellm_params. A user with team administrator access can read any environment variable of the proxy process, including the proxy master key, by registering a model whose api_key is an os.environ/<NAME> reference and whose api_base points to a host they control, then invoking it so that get_secret resolves the variable and _resolve_db_litellm_param sends it to that host as the outbound Authorization header. This requires STORE_MODEL_IN_DB to be enabled and an enterprise license, which is what makes the team administrator role available.

Note: A fix is unlikely. In https://github.com/BerriAI/litellm/commit/5862be3e79154ce5ac8a736c77c7c3614fac40fb, project maintainers removed the field whitelist and the team-scope short-circuit in _resolve_db_litellm_param deliberately, describing universal os.environ/ resolution for team-scoped rows as an intended threat-model expansion that trusts team administrators to read environment variables, and placing the trust boundary on who the deployment grants team administrator rather than on what those administrators may reference.

How to fix Authorization Bypass Through User-Controlled Key?

There is no fixed version for litellm.

[1.93.0.dev2,)

Weak Authentication

litellm is a Library to easily interface with LLM API providers

Affected versions of this package are vulnerable to Weak Authentication via the JWT authentication flow's email-based fallback lookup, which does not verify the email_verified claim before resolving a user identity. An attacker holding a valid JWT from the configured identity provider can present a token containing an unverified email address that matches a victim's account, causing the system to authenticate the attacker as that victim and inherit their role, including proxy_admin privileges. This also permanently overwrites the victim's stored identity binding, granting the attacker persistent unauthorized access to administrative endpoints that expose API keys and user management functions.

How to fix Weak Authentication?

There is no fixed version for litellm.

[0,)

Incorrect Authorization

litellm is a Library to easily interface with LLM API providers

Affected versions of this package are vulnerable to Incorrect Authorization via a tenant isolation bypass vulnerability in the semantic cache layer that allows authenticated users to read other tenants' cached responses by exploiting a metadata key mismatch between _get_semantic_cache_tenant_scope() and _get_metadata_variable_name(). Attackers holding a valid virtual key can submit semantically similar prompts on affected routes such as /v1/responses and /bedrock/* to retrieve cached responses containing other tenants' personally identifiable information, financial data, or source code, and can cause agentic front-ends to auto-execute attacker-supplied tool calls under victim credentials by returning cached function_call or tool_calls payloads to a different principal.

How to fix Incorrect Authorization?

Upgrade litellm to version 1.101.0rc1 or higher.

[,1.101.0rc1)

Insufficient Session Expiration

litellm is a Library to easily interface with LLM API providers

Affected versions of this package are vulnerable to Insufficient Session Expiration in the get_redirect_response_from_openid() function of the SSO Authentication Flow process. An attacker can cause premature session termination by manipulating authentication responses remotely, potentially leading to unauthorized session expiration and disruption of user access.

How to fix Insufficient Session Expiration?

There is no fixed version for litellm.

[0,)

Missing Authentication for Critical Function

litellm is a Library to easily interface with LLM API providers

Affected versions of this package are vulnerable to Missing Authentication for Critical Function in the /sso/debug/login and /sso/debug/callback endpoints in the SSO Debug Flow. An attacker can gain unauthorized access and potentially manipulate sensitive information by sending crafted requests to the affected endpoint.

How to fix Missing Authentication for Critical Function?

There is no fixed version for litellm.

[0,)

Incorrect Authorization

litellm is a Library to easily interface with LLM API providers

Affected versions of this package are vulnerable to Incorrect Authorization in the user_api_key_auth.py file of the M2M JWT Handler. An attacker can gain unauthorized access to resources by exploiting insufficient authorization checks.

Note: This is only exploitable if the attacker possesses valid but limited credentials and can craft specific JWTs to bypass intended access controls.

How to fix Incorrect Authorization?

There is no fixed version for litellm.

[0,)

Insufficient Session Expiration

litellm is a Library to easily interface with LLM API providers

Affected versions of this package are vulnerable to Insufficient Session Expiration in the authenticate_user function. An attacker can gain unauthorized access or maintain access to sensitive information by exploiting session management flaws.

How to fix Insufficient Session Expiration?

There is no fixed version for litellm.

[0,)

litellm@1.100.4

Library to easily interface with LLM API providers

latest version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically