Advisory

GHSA-jjhc-v7c2-5hh6

Also known as: CVE-2026-35030, PYSEC-2026-390

Summary

LiteLLM: Authentication bypass via OIDC userinfo cache key collision

Details

Impact

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.

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.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2026-04-03 21:59 UTC
Modified
2026-11-16 15:30 UTC

Affected packages and fixes

litellm

PyPI · All systems

Affected

  • introduced 0, fixed 1.83.0 (ecosystem)

Fixed versions

1.83.0

Fix

  • Fixed version 1.83.0
    pip install --upgrade litellm==1.83.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences