BerriAI LiteLLM: Exploited Flaw CVE-2026-59822
Published October 25, 2026 · Last updated October 25, 2026
What happened: On September 2, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-59822, a flaw in BerriAI LiteLLM, to its Known Exploited Vulnerabilities (KEV) catalog. The catalog lists flaws CISA has evidence attackers are using. CISA calls this one the "BerriAI LiteLLM Improper Authentication Vulnerability."
CISA's summary: "BerriAI LiteLLM contains an improper authentication vulnerability in the MCP Streamable HTTP endpoint that could allow an unauthenticated attacker to establish an authenticated MCP session using an arbitrary Bearer token."
What the National Vulnerability Database says
NVD first published CVE-2026-59822 on July 8, 2026. Its description, from the record's source ([email removed]), reads: "LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.84.0, LiteLLM's MCP Streamable HTTP endpoint allowed an unauthenticated attacker to use a fabricated Authorization header to trigger an OAuth2 passthrough fallback path that replaced failed LiteLLM key validation with an empty UserAPIKeyAuth() object, allowing requests to reach MCP tooling without a valid LiteLLM key. This issue is fixed in version 1.84.0."
How serious is CVE-2026-59822?
The CVSS 3.1 base score is 8.2 out of 10 (High), scored by nist.gov. In plain terms: an attacker can reach the LiteLLM weakness over a network, including the internet; the attacker does not need an account; no one has to click or open anything. The listed impact on LiteLLM data secrecy is high, on data integrity low, and on availability none. The full vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N.
Which LiteLLM versions are affected?
The CVE record lists these affected ranges:
- version < 1.84.0
If your LiteLLM version falls in one of these ranges, check BerriAI's advisory for the fixed release that applies to you.
What kind of weakness is it?
CISA and NVD map CVE-2026-59822 to the following weakness types in MITRE's Common Weakness Enumeration (CWE):
- CWE-287: Improper Authentication. MITRE's definition: "When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct."
- CWE-306: Missing Authentication for Critical Function. MITRE's definition: "The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources."
CISA required action for CVE-2026-59822
CISA's required action for this KEV catalog entry, quoted from the catalog record, is: "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines."
Timeline for CVE-2026-59822
- July 8, 2026: NVD publishes CVE-2026-59822.
- September 16, 2026: due date for U.S. federal civilian agencies to act on CVE-2026-59822.
- September 2, 2026: CISA adds CVE-2026-59822 to the KEV catalog.
- September 3, 2026: latest change to the NVD record (status: Analyzed).
Other scores in the NVD record: the address listed on github.com scores it 8.8 (High) under CVSS 4.0.
Advisories and technical references
The NVD record for CVE-2026-59822 links to these references; tags in brackets are NVD's labels:
- github.com/BerriAI/litellm/commit/73869f0faf7d11ee21adcb5f91b8c33a340b6c2c (Patch)
- github.com/BerriAI/litellm/pull/26463 (Issue Tracking, Patch)
- github.com/BerriAI/litellm/releases/tag/v1.84.0 (Product, Release Notes)
- github.com/BerriAI/litellm/security/advisories/GHSA-7488-6r32-c95q (Mitigation, Patch)
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-59822 (US Government Resource)
- www.wiz.io/blog/ai-infrastructure-honeypot (Third Party Advisory)
What to do
- Run BerriAI LiteLLM? Follow BerriAI's own advisory (linked under Sources) and apply the fix or mitigation it lists. CISA's required action for this entry is to apply the vendor's mitigations, or stop using the product if no mitigation is available.
- Federal civilian agencies must act by September 16, 2026, CISA's due date for this entry. Other organizations can use that date as a deadline for LiteLLM too.
- Ransomware use: CISA lists known ransomware campaign use for CVE-2026-59822 as "Unknown".
- Don't run LiteLLM yourself? You don't need to install anything on your phone or home computer for this. If a call, text, or pop-up says your device is infected by "CVE-2026-59822" and asks for payment or remote access, that is a scam pattern, not a BerriAI alert.
CVE-2026-59822 record details from CISA and NVD
- CISA forensic triage flag for CVE-2026-59822: No
- Attack complexity for CVE-2026-59822: low
- CVE-2026-59822 CVSS scope: unchanged
- NVD sub-scores for CVE-2026-59822: exploitability 3.9, impact 4.2.
- Who mapped the weakness type: the address listed on github.com (Secondary)
- NVD product identifiers (CPE):
cpe:2.3:a:litellm:litellm:*:*:*:*:*:*:*:* - References in the NVD record: 6 (3 tagged Patch, 1 tagged Issue Tracking, 1 tagged Product).
- CISA SSVC decision points for CVE-2026-59822 (from NVD): exploitation=active; automatable=yes; technicalImpact=partial (role: CISA Coordinator, SSVC 2.0.3).
Sources
General education only, not security advice. Facts checked against the sources above on the date shown.