---
schema_version: '1.0'
id: security-20260711-c3dbc4
url: https://osv.dev/vulnerability/PYSEC-2026-390
url_hash: c3dbc444bc27fbb9d819d62ade50bf5df62bf6e5facd9cb0595619c3f49fd1dc
canonical_url: https://osv.dev/vulnerability/PYSEC-2026-390
source: osv:pypa
category: security/library
category_raw: cve/library
region: null
tags:
- cve
- CVE-2026-35030
- PYSEC-2026-390
- severity: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
- litellm
- PyPI
lang: en
published_at: '2026-06-29T11:50:47Z'
fetched_at: '2026-07-11T06:37:17Z'
updated_at: '2026-07-11T06:39:11Z'
status: published
content_hash: c5ac9d03f131ef8ec2a28ee9d4df7b05210365952d7610fc153cf157971e199b
license_note: full
summary: 'LiteLLM: Authentication bypass via OIDC userinfo cache key collision'
summary_source: rss
summary_en: 'LiteLLM: Authentication bypass via OIDC userinfo cache key collision'
entities:
- name: VIATRIX
  type: artifact
key_facts: []
related: []
related_auto:
- name: 傲鲨
  type: organization
  weight: 1.0
title: 'CVE-2026-35030: LiteLLM: Authentication bypass via OIDC userinfo cache key
  collision'
---

# CVE-2026-35030: LiteLLM: Authentication bypass via OIDC userinfo cache key collision

## TL;DR
LiteLLM: Authentication bypass via OIDC userinfo cache key collision

## Key Points
- cve / CVE-2026-35030 / PYSEC-2026-390 / severity: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 / litellm / PyPI

## Details
**Severity:** 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
**Advisory:** PYSEC-2026-390 (CVE-2026-35030)

**Affected (your watchlist):**
- `PyPI:litellm` 1.72.6.post2 → fixed in 1.83.0 [docker/docker-strands]

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

**References:**
- https://github.com/BerriAI/litellm/security/advisories/GHSA-jjhc-v7c2-5hh6
- https://nvd.nist.gov/vuln/detail/CVE-2026-35030
- https://github.com/BerriAI/litellm
- https://pypi.org/project/litellm
- https://github.com/advisories/GHSA-jjhc-v7c2-5hh6

_Data: OSV.dev (upstream: pypa) — https://osv.dev/vulnerability/PYSEC-2026-390_

## Source
元記事: [CVE-2026-35030: LiteLLM: Authentication bypass via OIDC userinfo cache key collision](https://osv.dev/vulnerability/PYSEC-2026-390) — published 2026-06-29T11:50:47Z