CVE Feed
9.4 Critical

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format.

CVE-2026-35030

Impact When JWT authentication is enabled (enablejwtauth: 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. Patches Fixed in v1.83.0. The cache key now uses the full hash of the JWT token. Workarounds Disable OIDC userinfo caching by setting the cache TTL to 0, or disable JWT authentication entirely.

Proof-of-concept code is published

Public PoC

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Part of the AI stack

This affects LiteLLM, in Inference & serving.

Assessment

CVSS
9.4 (v4.0)
Severity
Critical
EPSS
0.63% chance of exploitation in the next 30 days
Known exploited
Not listed in CISA KEV
Exploit availability
Public PoC
Published
3 April 2026
Last updated
24 October 2026
Affected
berriai · LiteLLM · litellm
Weakness
CWE-222, CWE-287
Assigner
security-advisories@github.com

CVSS vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-35030