CVE-2026-35030 | BerriAI litellm up to 1.82.x JWT/OIDC enable_jwt_auth improper authentication (GHSA-jjhc-v7c2-5hh6)

VDB-355611 · CVE-2026-35030 · GHSA-JJHC-V7C2-5HH6 BERRIAI LITELLM UP TO 1.82.X JWT/OIDC ENABLE_JWT_AUTH IMPROPER AUTHENTICATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.0 $0-$5k 2.24+ Summaryinfo A vulnerability marked as critical has been reported in BerriAI litellm up to 1.82.x. This vulnerability affects the function enable_jwt_auth of the component JWT/OIDC. Performing a manipulation results in improper authentication. This vulnerability is identified as CVE-2026-35030. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component. Detailsinfo A vulnerability, which was classified as critical, was found in BerriAI litellm up to 1.82.x. This affects the function enable_jwt_auth of the component JWT/OIDC. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is: 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. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-35030 since 03/31/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. Upgrading to version 1.83.0 eliminates this vulnerability. Productinfo Vendor BerriAI Name litellm Version 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 1.33 1.34 1.35 1.36 1.37 1.38 1.39 1.40 1.41 1.42 1.43 1.44 1.45 1.46 1.47 1.48 1.49 1.50 1.51 1.52 1.53 1.54 1.55 1.56 1.57 1.58 1.59 1.60 1.61 1.62 1.63 1.64 1.65 1.66 1.67 1.68 1.69 1.70 1.71 1.72 1.73 1.74 1.75 1.76 1.77 1.78 1.79 1.80 1.81 1.82 Website Product: https://github.com/BerriAI/litellm/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 7.3 VulDB Meta Temp Score: 7.0 VulDB Base Score: 7.3 VulDB Temp Score: 7.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Improper authentication CWE: CWE-287 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: litellm 1.83.0 Timelineinfo 03/31/2026 CVE reserved 04/06/2026 +6 days Advisory disclosed 04/06/2026 +0 days VulDB entry created 04/06/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-jjhc-v7c2-5hh6 Status: Confirmed CVE: CVE-2026-35030 (🔒) GCVE (CVE): GCVE-0-2026-35030 GCVE (VulDB): GCVE-100-355611 Entryinfo Created: 04/06/2026 19:34 Changes: 04/06/2026 19:34 (69) Complete: 🔍 Cache ID: 99:AA6:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸