Skip to content

Bump litellm from 1.82.2 to 1.83.0 (CVE-2026-35030)#95

Open
chenosgabbay wants to merge 1 commit intoshcherbak-ai:mainfrom
chenosgabbay:fix/bump-litellm-cve-2026-35030
Open

Bump litellm from 1.82.2 to 1.83.0 (CVE-2026-35030)#95
chenosgabbay wants to merge 1 commit intoshcherbak-ai:mainfrom
chenosgabbay:fix/bump-litellm-cve-2026-35030

Conversation

@chenosgabbay
Copy link
Copy Markdown

Summary

Bump the pinned litellm version from 1.82.2 to 1.83.0 to fix CVE-2026-35030 (GHSA-jjhc-v7c2-5hh6).

Vulnerability

litellm < 1.83.0 has an OIDC authentication bypass via JWT cache collision. The OIDC userinfo caching mechanism uses only the first 20 characters of a JWT token as the cache key. Since tokens generated by the same signing algorithm share identical initial characters, an attacker can craft a malicious token matching a legitimate user's cached token prefix, gaining unauthorized access.

The fix in 1.83.0 changes the cache key to use the full hash of the JWT token.

Reference

Impact

This is a single-line change to pyproject.toml — only the pinned litellm version number. No other dependencies or code are affected.

litellm < 1.83.0 is vulnerable to OIDC authentication bypass via JWT
cache collision (CVE-2026-35030 / GHSA-jjhc-v7c2-5hh6). The flaw is in
the OIDC userinfo caching mechanism which uses only the first 20
characters of a JWT token as the cache key, allowing an attacker to
craft a token that collides with a legitimate user's cached entry.

Bump the pinned version to 1.83.0 which fixes the cache key to use
the full hash of the JWT token.

Reference: GHSA-jjhc-v7c2-5hh6

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant