Lookup for vulnerable packages by Package URL.
| Purl | pkg:pypi/litellm@1.65.6 |
|---|
| Type | pypi |
|---|
| Namespace | |
|---|
| Name | litellm |
|---|
| Version | 1.65.6 |
|---|
| Qualifiers |
|
|---|
| Subpath | |
|---|
| Is_vulnerable | true |
|---|
| Next_non_vulnerable_version | 1.83.10 |
|---|
| Latest_non_vulnerable_version | 1.83.10 |
|---|
| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-362j-e9vs-73gg |
| vulnerability_id |
VCID-362j-e9vs-73gg |
| summary |
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. |
| references |
| 0 |
|
| 1 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2026-35030 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.00048 |
| scoring_system |
epss |
| scoring_elements |
0.15613 |
| published_at |
2026-06-12T12:55:00Z |
|
| 1 |
| value |
0.00048 |
| scoring_system |
epss |
| scoring_elements |
0.15477 |
| published_at |
2026-06-11T12:55:00Z |
|
| 2 |
| value |
0.00064 |
| scoring_system |
epss |
| scoring_elements |
0.2032 |
| published_at |
2026-06-14T12:55:00Z |
|
| 3 |
| value |
0.00064 |
| scoring_system |
epss |
| scoring_elements |
0.20342 |
| published_at |
2026-06-13T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2026-35030 |
|
| 2 |
|
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
|
| 7 |
|
|
| fixed_packages |
|
| aliases |
CVE-2026-35030, GHSA-jjhc-v7c2-5hh6
|
| risk_score |
4.5 |
| exploitability |
0.5 |
| weighted_severity |
9.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-362j-e9vs-73gg |
|
| 1 |
| url |
VCID-jw3v-fdn2-bugj |
| vulnerability_id |
VCID-jw3v-fdn2-bugj |
| summary |
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. |
| references |
| 0 |
|
| 1 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2026-35029 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.1938 |
| scoring_system |
epss |
| scoring_elements |
0.95538 |
| published_at |
2026-06-12T12:55:00Z |
|
| 1 |
| value |
0.1938 |
| scoring_system |
epss |
| scoring_elements |
0.95524 |
| published_at |
2026-06-11T12:55:00Z |
|
| 2 |
| value |
0.21671 |
| scoring_system |
epss |
| scoring_elements |
0.95878 |
| published_at |
2026-06-14T12:55:00Z |
|
| 3 |
| value |
0.21671 |
| scoring_system |
epss |
| scoring_elements |
0.95875 |
| published_at |
2026-06-13T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2026-35029 |
|
| 2 |
|
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
|
| 7 |
|
| 8 |
|
|
| fixed_packages |
|
| aliases |
CVE-2026-35029, GHSA-53mr-6c8q-9789
|
| risk_score |
4.0 |
| exploitability |
0.5 |
| weighted_severity |
8.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-jw3v-fdn2-bugj |
|
| 2 |
| url |
VCID-tssn-kdqp-jbez |
| vulnerability_id |
VCID-tssn-kdqp-jbez |
| summary |
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. |
| references |
|
| fixed_packages |
|
| aliases |
GHSA-69x8-hrgq-fjj8
|
| risk_score |
4.0 |
| exploitability |
0.5 |
| weighted_severity |
8.0 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-tssn-kdqp-jbez |
|
|
|---|
| Fixing_vulnerabilities |
|
|---|
| Risk_score | 4.5 |
|---|
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:pypi/litellm@1.65.6 |
|---|