---
id: "CVE-2026-35030"
page: "https://infrastack.ai/live/CVE-2026-35030"
kind: "vulnerability"
aliases: ["CVE-2026-35030", "GHSA-jjhc-v7c2-5hh6"]
title: "LiteLLM: Authentication bypass via OIDC userinfo cache key collision"
severity: "critical"
cvss: 9.4
epss: 0.00636
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "litellm", "fixed": ["1.83.0"], "affected": "< 1.83.0", "ecosystem": "pypi"}, {"name": "litellm", "fixed": ["1.83.0"], "affected": "< 1.83.0", "ecosystem": "vendor"}]
ecosystems: ["pypi", "vendor"]
tags: ["ai-tooling", "cwe-222", "cwe-287", "litellm", "llm-gateway", "python", "self-hosted"]
not_affected_if: ["default-config", "jwt-auth-disabled"]
published_at: "2026-04-03T21:59:50+00:00"
first_seen_at: "2026-11-16T15:12:10+00:00"
updated_at: "2026-11-16T15:37:59+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-jjhc-v7c2-5hh6", "first_seen_at": "2026-11-16T15:12:10+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-35030", "first_seen_at": "2026-11-16T15:37:59+00:00"}]
exploit_sources: [{"type": "epss", "score": 0.00636, "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-35030"}]
---

# LiteLLM: Authentication bypass via OIDC userinfo cache key collision

Link for people: https://infrastack.ai/live/CVE-2026-35030 (this .md is for agents)

When JWT authentication is enabled, LiteLLM caches OIDC userinfo keyed on the first 20 characters of the token, and tokens from the same signing algorithm share that prefix. An unauthenticated attacker can craft a token that hits a legitimate user's cache entry and inherits that user's identity and permissions.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- pypi:litellm affected < 1.83.0 fixed 1.83.0
- vendor:litellm affected < 1.83.0 fixed 1.83.0

## How to check

- Check the proxy configuration for `enable_jwt_auth: true`; if it is absent or false, the instance is not affected.
- Check the installed version with `pip show litellm`; versions below `1.83.0` are affected.
- Check whether OIDC userinfo caching is active (cache TTL not set to `0`).

## Fix

- `litellm` (PyPI): move to `1.83.0` or later.

## Timeline

- 2026-11-16T15:12:10+00:00 ghsa https://github.com/advisories/GHSA-jjhc-v7c2-5hh6
- 2026-11-16T15:37:59+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-35030

## Documents

- [advisory] Maintainer's advisory: api.github.com https://api.github.com/repos/BerriAI/litellm/security-advisories/GHSA-jjhc-v7c2-5hh6
- [advisory] Maintainer's advisory: github.com https://github.com/BerriAI/litellm/security/advisories/GHSA-jjhc-v7c2-5hh6

## From the sources

###  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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
