Description
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, 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. Fixed in v1.83.0.
References
- www.cve.org/CVERecord ↗
- nvd.nist.gov/vuln/detail/CVE-2026-35030 ↗
- github.com/BerriAI/litellm/security/advisories/GHSA-jjhc-v7c2-5hh6 ↗
- access.redhat.com/errata/RHSA-2026:13545 ↗
- access.redhat.com/errata/RHSA-2026:28960 ↗
- access.redhat.com/errata/RHSA-2026:30056 ↗
- access.redhat.com/security/cve/CVE-2026-35030 ↗
- bugzilla.redhat.com/show_bug.cgi ↗
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35030.json ↗
Related CVEs
← CVE Index: search every CVE from the last 30 days
This product uses the NVD API but is not endorsed or certified by the NVD. CVSS scores do not establish exploitation.