LiteLLM JWT Migration Regression: DB Key Leakage & Privilege Escalation via Stateless JWT Tokens

Vulnerability Overview Title: JWT Migration Regression — /login Still Generates Permanent DB Keys Leaked Inside Stateless JWT Tokens Description: During the JWT migration in the Admin UI, the call was not removed from the login flow. Every and request creates a new database API key, which is embedded into the JWT cookie (without the secret field), and previous keys are not invalidated. An attacker can intercept any login cookie, decode the JWT (no secret key required), extract the key, and use it as an independent administrator bearer token that remains valid even after the JWT session expires. Impact Scope Affected Products: - Ecosystem: PyPI - Package Name: litellm - Affected Versions: <= 1.82.2 (latest version at the time of discovery) - Fixed Versions: None Severity: High Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Weaknesses: - CWE-613: Insufficient Session Expiration - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor Remediation Remediation Status: No specific fix mentioned, but it is noted that the previous fix function was completely removed during the JWT migration, leading to this regression. POC Code 1. Login and Capture JWT Cookie 2. Decode JWT and Extract Embedded DB Key (No Key Required) 3. Use the Extracted Key as an Independent Administrator API Key Returns HTTP 200 — Full administrator access. 4. Repeat Login to Demonstrate Key Accumulation (Keys Never Expire) Evidence Logs Occurrence Permanent Links: - Admin login path - User login path - Key embedded in JWT - /onboarding/get_token endpoint Description: - Admin login path: creates permanent DB keys, despite the JWT migration aiming to eliminate DB keys. - User login path: The same call creates additional accumulating DB keys for regular users. - Key embedded in JWT: embeds the physical DB key into the JWT payload, leaking it via , which is extractable by simply base64-decoding the JWT without needing the signing key. - /onboarding/get_token endpoint: The same call creates accumulating DB keys and embeds them in the JWT.

Goal Reached Thanks to every supporter — we hit 100%!

LiteLLM JWT Migration Regression: DB Key Leakage & Privilege Escalation via Stateless JWT Tokens