Skip to content

CVE-2026-59822

Improper Authentication: Is CVE-2026-59822 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

Give your verdict☆ Watch

signals

public sources

Exploited in wild
Yes
CISA KEV · Sep 2, 2026
Public exploit
PoC (unverified)
Metasploit/EDB/PoC
Base severity
8.2 High
CVSS
Exploitation prob.
0.8%
FIRST EPSS
Weakness
CWE-287 · Improper Authentication
CWE

Confirmed exploited in the wild. Patch this first, regardless of the base score.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
Active
in the wild
Automatable
Yes
at scale
Technical impact
Partial
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Attend
  • medium impact → Attend
  • high impact → Act

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

public exploits

links to sources — we don’t host code
GitHub PoCunverified

Unverified proof-of-concept code has been published. It may or may not be functional — assess before relying on it.

affected packages

GHSA-7488-6r32-c95q · GitHub rates it high
  • PyPIlitellm
    Vulnerable
    < 1.84.0
    Fixed in
    1.84.0

Source: GitHub Advisory Database (CC-BY 4.0), via OSV.dev. Check your lockfile version against the ranges above.

baseline read

auto · not a community verdict

Real — exploited in the wild

CISA confirms active exploitation. Treat scanner hits as true positives unless your specific version or config is unaffected.

Based on CISA KEV

Confirm or dispute →
Affected:Litellm

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

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.

References

NVD MITRE CVE.org CISA KEV VulnCheck KEV

Published · Added to CISA KEV (56 days after publication)

Embed this verdict
TruePositive verdict for CVE-2026-59822
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-59822/badge.svg)](https://www.truepositive.app/cve/CVE-2026-59822)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-59822"><img src="https://www.truepositive.app/cve/CVE-2026-59822/badge.svg" alt="TruePositive verdict for CVE-2026-59822"></a>

Live badge that updates automatically as the community verdict changes.

timeline

  1. CISA SSVC assessment · exploitation: active
  2. Added to CISA KEV · confirmed exploited in the wild
  3. Published by NVD
  4. Added to VulnCheck KEV · reported exploited in the wild

Score and exploit changes tracked since .

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: TruePositive's read from public sources is Real & exploitable — a starting point, not a community verdict.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    BerriAI LiteLLM Improper Authentication Vulnerability — 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. Listed in the CISA KEV catalog (added 2026-09-02) — confirmed exploited in the wild, not theoretical. FIRST EPSS puts the chance of exploitation in the next 30 days at ~1%. Treat it as real and prioritize remediation over triage.

  • 0
    Remediation · TruePositive EditorialCurated

    Required action for BerriAI LiteLLM: 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. CISA set a federal remediation due date of 2026-09-16. After patching, verify the vulnerable path is no longer reachable before closing the finding.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Related CVEs

Same weakness: CWE-287 · Improper Authentication.