Skip to main content
VulnerabilityPublished Updated

CVE-2026-35030: BerriAI litellm · Improper Authentication

Affects BerriAI litellmSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.4 Critical : upgrade to 1.83.0 as a priority.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.83.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade litellm and berriai/litellm to 1.83.0.

Affected software

ProductAffectedFixed in
BerriAIlitellmAffected
  • <1.83.0
Fixed in
  • 1.83.0
GitHubberriai/litellmpkg:github/berriai/litellmOther threatsAffected
  • <1.83.0
Fixed in
  • 1.83.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version, litellm 1.83.0, is available and should be applied to remediate this vulnerability. Deployments that do not have JWT/OIDC authentication enabled are not affected. Patch status is confirmed by the vendor advisory. Users should upgrade to version 1.83.0 or later to resolve this issue.

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

Community reviews

Loading reviews…