SSRF (Server-Side Request Forgery) in litellm (CVE-2026-59823)
Summary
SSRF in litellm (CVE-2026-59823). Risk of unauthorized operations or information disclosure. Exploitable via api_base. Mitigation: upgrade to 1.83.9 or later.
Original description
The description as published by the source.
Summary
A server-side request forgery in LiteLLM Proxy lets an authenticated caller redirect the
proxy's outbound request to a host of their choosing by smuggling an api_base inside the
user_config request body, bypassing the existing parameter guard.
Details
LiteLLM Proxy validates request bodies with is_request_body_safe, which blocks the
api_base and base_url parameters but does not cover user_config. The user_config
object is used to build the outbound router for a request, so a caller can place an
api_base inside it and reach an arbitrary host. The guard only inspected the two
top-level keys, so the same api_base nested inside user_config was never checked.
Exploitation requires a valid virtual key.
Impact
An authenticated caller can make the proxy issue server-side requests to internal or
external hosts of their choosing, reaching endpoints the caller cannot otherwise access.
Affected / Patched
Affected: <= 1.83.8
Patched: 1.83.9
Remediation
Upgrade to 1.83.9 or later (released 2026-04-17).
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59823 has been found in litellm.
Attackers can target a specific entry point like api_base over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade litellm to 1.83.9 or later.
If unsure, ask your IT team or search "litellm CVE-2026-59823" on the vendor's site.
CVE-2026-59823 (litellm) — CWE-918
Attack surface: api_base / user_config / is_request_body_safe / base_url
Patched: 1.83.9 — apply immediately
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.
SSRF (CWE-918) exists in litellm. Attackers reach the vulnerable code path via api_base.
Check the vendor advisory for the affected versions of litellm. Attack surface: api_base / user_config / is_request_body_safe / base_url.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.83.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade litellm to 1.83.9ステージング環境で 1.83.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com