← Back
CVE-2026-59822
high
CVSS 8.2
Authentication Bypass in litellm (CVE-2026-59822)
Summary
authentication bypass in litellm (CVE-2026-59822). Confidential information can be exposed externally. Exploitable via ``Authorization``. Mitigation: upgrade to `1.84.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59822** has been found in litellm.
Attackers can target a specific entry point like ``Authorization`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade litellm to **1.84.0** or later.
If unsure, ask your IT team or search "litellm CVE-2026-59822" on the vendor's site.
CVE-2026-59822 (litellm) — CWE-287 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `Authorization`
Patched: `1.84.0` — apply immediately
Workaround: If upgrading is not immediately possible, disable MCP routes or block access to `/mcp/` and related MCP endpoints at your reverse proxy or API gateway.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**authentication bypass** (CWE-287) exists in litellm. Attackers reach the vulnerable code path via ``Authorization`` without authentication.
📍 Affected scope
litellm — . Attack surface: `Authorization`.
🔥 Severity
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.84.0**.
🛡️ Workaround
Workaround: If upgrading is not immediately possible, disable MCP routes or block access to `/mcp/` and related MCP endpoints at your reverse proxy or API gateway.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'litellm' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'litellm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `litellm` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
If upgrading is not immediately possible, disable MCP routes or block access to `/mcp/` and related MCP endpoints at your reverse proxy or API gateway.パッチが適用されるまでの応急処置として、If upgrading is not immediately possible, disable MCP routes or block access to `/mcp/` and related MCP endpoints at your reverse proxy or API gateway. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade litellm to 1.84.0ステージング環境で 1.84.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
litellm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.84.0"}]}]