CVE-2026-93355: Weak Authentication in BerriAI litellm
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.
AI Analysis
Technical Summary
CVE-2026-93355 describes a weak authentication vulnerability in BerriAI's LiteLLM product. The issue arises because the JWT authentication flow uses an email-based fallback lookup that does not verify the email_verified claim. An attacker possessing a valid JWT with an unverified email matching a victim's account can authenticate as that user, inheriting their roles including proxy_admin privileges. This allows the attacker to permanently overwrite the victim's stored identity binding, maintaining persistent unauthorized access to administrative endpoints that expose API keys and user management functions.
Potential Impact
Attackers can impersonate any existing user by exploiting the lack of email verification in the JWT authentication fallback. This leads to unauthorized privilege escalation to administrative roles, persistent identity binding overwrites, and exposure of sensitive administrative API keys and user management capabilities. The vulnerability poses a high risk to confidentiality and integrity of the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict JWT token issuance to trusted identity providers and monitor for suspicious token usage. Avoid relying on email-based fallback lookups without verifying the email_verified claim.
CVE-2026-93355: Weak Authentication in BerriAI litellm
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.
CVSS v4.0
Score 7.6high
Affected software
BerriAI
litellm
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-93355 describes a weak authentication vulnerability in BerriAI's LiteLLM product. The issue arises because the JWT authentication flow uses an email-based fallback lookup that does not verify the email_verified claim. An attacker possessing a valid JWT with an unverified email matching a victim's account can authenticate as that user, inheriting their roles including proxy_admin privileges. This allows the attacker to permanently overwrite the victim's stored identity binding, maintaining persistent unauthorized access to administrative endpoints that expose API keys and user management functions.
Potential Impact
Attackers can impersonate any existing user by exploiting the lack of email verification in the JWT authentication fallback. This leads to unauthorized privilege escalation to administrative roles, persistent identity binding overwrites, and exposure of sensitive administrative API keys and user management capabilities. The vulnerability poses a high risk to confidentiality and integrity of the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict JWT token issuance to trusted identity providers and monitor for suspicious token usage. Avoid relying on email-based fallback lookups without verifying the email_verified claim.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-17T18:41:40.758Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6abac483f7a7c541061ff40e
Added to database: 09/28/2026, 19:48:19 UTC
Last enriched: 09/28/2026, 20:02:39 UTC
Last updated: 09/29/2026, 01:57:22 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.