Skip to content
AgentProv

2026-04-15 · 2026-Q2

LiteLLM OIDC Userinfo Cache Authentication Bypass

Primary layerL6 Identity / RunSecondary:L1 Credential

Which agent, run, or tenant is this?

The question layer 6 asks, and failed here.
Fixable
Vendor patch
Vendor response
Unknown
In the wild
No
Actor
Attacker

Target

LiteLLM (BerriAI LLM gateway) deployments with JWT auth enabled

Impact

Unauthenticated attacker can craft a token whose first 20 characters collide with a cached legitimate token, inheriting that user's identity and permissions across the gateway

Root cause

OIDC userinfo cache keyed on token[:20] instead of the full token or a secure hash; JWTs produced by the same signing algorithm share the same header prefix

CVE

Sources

Catalog

Cite this: AgentProv incident record: LiteLLM OIDC Userinfo Cache Authentication Bypass (2026-04-15). https://agentprov.com/incidents/2026-04-15-litellm-oidc-userinfo-cache-authentication-bypass