Critical

LiteLLM: Authentication bypass via OIDC userinfo cache key collision

  • Disclosed: 03.04.2026
  • Updated: 11.10.2026 15:17

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) litellm < 1.83.0 1.83.0

References

CVSS score -
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Weakness (CWE)
CWE-287
Platform
Python (PyPI)
Package
litellm
Disclosed
03.04.2026
Updated
11.10.2026 15:17

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-390 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-jjhc-v7c2-5hh6 - CC BY 4.0

Vulnerability history: litellm

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (42) in the archive
Total entries
42
First → latest
04.2024 09.2026
Without a fix
14
Exploited in attacks
3

Severity breakdown

  • Critical 7
  • High 17
  • Medium 8
  • Low 9
  • Unrated 1

Disclosures per year

  1. 2024: 8
  2. 2025: 6
  3. 2026: 28
Severity:
  1. High Exploited in attacks CVE-2026-59822 < 1.84.0 1.84.0
  2. Critical · 9.8 CVE-2026-49468 < 1.84.0 1.84.0
  3. High · 8.8 CVE-2026-40217 >= 1.81.8, < 1.83.10 1.83.10
  4. High · 8.8 Exploited in attacks CVE-2026-42271 >= 1.74.2, < 1.83.7 1.83.7
  5. Critical · 9.8 Exploited in attacks CVE-2026-42208 >= 1.81.16, < 1.83.7 1.83.7
  6. High CVE-2026-42203 >= 1.80.5, < 1.83.7 1.83.7
  7. LiteLLM: Authentication bypass via OIDC userinfo cache key collision this entry
    Critical CVE-2026-35030 < 1.83.0 1.83.0
  8. Critical ghsa-5mg7-485q-xm76 >= 1.82.7, <= 1.82.8 no fix
  9. High · 8.1 CVE-2025-0628 < 1.61.15 1.61.15
  10. High · 7.5 CVE-2025-0330 <= 1.52.1 no fix
  11. High · 7.5 CVE-2024-9606 < 1.44.12 1.44.12
  12. High · 8.8 CVE-2024-6825 >= 1.40.3.dev2, <= 1.40.12 no fix
  13. High · 7.5 CVE-2024-10188 < 1.53.1.dev1 1.53.1.dev1
  14. High · 7.5 CVE-2024-6587 < 1.44.8 1.44.8
Show more (4) Showing 20 of 24

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.