Vulnerability Intelligence Report
LiteLLM has an authentication bypass via OIDC userinfo cache key collision
CVE-2026-35030
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.
Authentication Bypass
No Active Exploit Signals
CVSS Base Score
9.4
CRITICAL
EPSS Probability:0.49%
Executive Threat Verdict
Evaluating...
Evaluating Threat Landscape...
Assessing known weaponization, exploitation telemetry, and federal advisories.
Attack Surface
—
Authentication
—
Weaponization
—
SSVC Action
—
Weaknesses (CWE)
CWE-287 ↗CWE-287: Improper Authentication
Affected Products & Versions
| Vendor | Product | Affected Versions |
|---|---|---|
| BerriAI | litellm | < 1.83.0 (affected) |
References & Technical Advisories
No reference links found.
Threat Intelligence Signals
Identity & Timeline
| Status | PUBLISHED |
| Assigning Authority | GitHub, Inc. · Vendor · USA |
| Reserved | 2026-03-31T21:06:06 |
| Published | 2026-04-06T16:47:02 |
| Last Updated | 2026-07-15T01:03:17 |
Community Chatter & Buzz