CVE-2026-35030: LiteLLM Authentication Bypass Vulnerability
CRITICALCVE-2026-35030 is a CRITICAL authentication bypass vulnerability (CWE-287: Improper Authentication) affecting LiteLLM libraries in the PyPI ecosystem. The issue involves authentication bypass via oidc userinfo cache key collision. Remediation is available by upgrading affected packages to version 1.83.0.
CVE-2026-35030 at a Glance
How to Fix CVE-2026-35030
To remediate this vulnerability, upgrade all affected LiteLLM dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install litellm>=1.83.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show litellm
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-35030, inspect your installed packages using pip:
pip show litellm
Analyze the terminal output to locate any version of LiteLLM in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.83.0), your application is affected.
Note: The pip show litellm command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In LiteLLM, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-35030 Affected LiteLLM Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
litellm
|
PyPI |
< 1.83.0
|
1.83.0
|
References
Frequently Asked Questions
What is CVE-2026-35030?
Which LiteLLM versions are affected?
What version fixes CVE-2026-35030?
Is litellm affected?
What CWE is associated with CVE-2026-35030?
How can I check PyPI dependencies for CVE-2026-35030?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-jjhc-v7c2-5hh6",
"modified" : "2026-04-06T23:40:39Z",
"published" : "2026-04-03T21:59:50Z",
"aliases" : [ "CVE-2026-35030" ],
"summary" : "LiteLLM: Authentication bypass via OIDC userinfo cache key collision",
"details" : "### Impact\n\nWhen 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.\n\nThis configuration option is not enabled by default. **Most instances are not affected.**\n\nAn 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.\n\n### Patches\n\nFixed in v1.83.0. The cache key now uses the full hash of the JWT token.\n\n### Workarounds\n\nDisable OIDC userinfo caching by setting the cache TTL to 0, or disable JWT authentication entirely.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "litellm"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.83.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/BerriAI/litellm/security/advisories/GHSA-jjhc-v7c2-5hh6"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-35030"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/BerriAI/litellm"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-287" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-03T21:59:50Z",
"nvd_published_at" : "2026-04-06T17:17:12Z"
}
}