Skip to main content
VulnerabilityPublished Updated

CVE-2026-89032: BerriAI litellm · Incorrect Authorization

Affects BerriAI litellmSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 1.101.0-rc.1 soon.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.101.0-rc.1
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade BerriAI litellm to 1.101.0-rc.1.

Affected software

ProductAffectedFixed in
BerriAIlitellmAffected
  • <1.101.0-rc.1
Fixed in
  • 1.101.0-rc.1
GitHublitellmpkg:github/litellmOther threatsAffected
  • <1.101.0-rc.1
Fixed in
  • 1.101.0-rc.1

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

AI-suggested

A fix is available in BerriAI LiteLLM version 1.101.0-rc.1 and later. Users should upgrade to this version or newer to remediate the vulnerability. Since this is not a cloud service, remediation requires applying the official patch. No vendor advisory content was provided to indicate alternative mitigations or temporary fixes.

Description

BerriAI LiteLLM before 1.101.0-rc.1 contains a tenant isolation bypass vulnerability in the semantic cache layer that allows authenticated users to read other tenants' cached responses by exploiting a metadata key mismatch between _get_semantic_cache_tenant_scope() and _get_metadata_variable_name(). Attackers holding a valid virtual key can submit semantically similar prompts on affected routes such as /v1/responses and /bedrock/* to retrieve cached responses containing other tenants' personally identifiable information, financial data, or source code, and can cause agentic front-ends to auto-execute attacker-supplied tool calls under victim credentials by returning cached function_call or tool_calls payloads to a different principal.

References

Community reviews

Loading reviews…