Browse / AI Framework and Platform Flaws / CVE-2026-35030
LiteLLM: Authentication bypass via OIDC userinfo cache key collision
- Class
- AI Framework and Platform Flaws (filed by a model that read the advisory)
- Technique
- Authentication and access control
- Affected
- litellm (PyPI)
- Gets past
- Authentication check
- CVSS
- 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
- EPSS
- 0.6% chance of exploitation in 30 days
How it works, in short
The OIDC userinfo cache keys on the first 20 characters of the JWT, so a forged token sharing that prefix gets the cached identity of a legitimate user. (Our summary, written by a model. The source text is below.)
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://access.redhat.com/errata/RHSA-2026:13545
- https://access.redhat.com/errata/RHSA-2026:28960
- https://access.redhat.com/errata/RHSA-2026:30056
- https://access.redhat.com/security/cve/CVE-2026-35030
- https://bugzilla.redhat.com/show_bug.cgi?id=2455509
- https://github.com/BerriAI/litellm
- https://github.com/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-390.yaml
- https://pypi.org/project/litellm
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35030.json
Source: GitHub Advisory Database, used under CC BY 4.0.