Description
LiteLLM contains a weak authentication vulnerability that allows an attacker holding a valid JWT from the configured identity provider to authenticate as any existing user by exploiting an email-based fallback lookup in the JWT authentication flow without verifying the email_verified claim. Attackers can present a token with an unverified email address matching a victim's account to inherit the victim's role, including proxy_admin privileges, and permanently overwrite the victim's stored identity binding to retain persistent unauthorized access to administrative endpoints exposing API keys and user management.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| BerriAI | litellm | ≤ 1.102.1 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Tumbleweed | python-litellm | 1.103.0-1.1 | openSUSE-SU-2026:11927-1 |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
GitHub 1 repository
-
InertFluid/cve-2026-93355-lab ★ 0 · Oct 7, 2026
Benign, offline reproduction of CVE-2026-93355 — LiteLLM unverified-email JWT account takeover (runs LiteLLM's real code)
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Advisories 2
- WID-SEC-2026-3617 LiteLLM: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen und potenziell Privilegieneskalation BSI CERT-Bund (WID) · Oct 4, 2026
- openSUSE-SU-2026:11927-1 python313-litellm-1.103.0-1.1 on GA media SUSE / openSUSE Security Updates · Sep 30, 2026
References
- OXsecurity Blog technical-description exploit
- https://www.vulncheck.com/advisories/litellm-weak-jwt-authentication-via-email-based-user-lookup third-party-advisory