Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-49468 critical CVSS 9.8

Vulnerability in litellm (CVE-2026-49468)

Summary

vulnerability in litellm (CVE-2026-49468). Successful exploitation can lead to full system takeover. Exploitable via ``request.url.path``. Mitigation: upgrade to `1.84.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-49468** has been found in litellm. Attackers can target a specific entry point like ``request.url.path`` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: 9.8/10. What to do: upgrade litellm to **1.84.0** or later. If unsure, ask your IT team or search "litellm CVE-2026-49468" on the vendor's site.
CVE-2026-49468 (litellm) — CWE-290 / CVSS v3 9.8 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `request.url.path` / `Host` / `server_name` Patched: `1.84.0` — apply immediately Workaround: If upgrading is not immediately possible, place the proxy behind an upstream component that validates or normalizes the `Host` header before forwarding (a CDN/WAF, a reverse proxy with explicit `server_name` allowlists, or a cloud load balancer with 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
**A vulnerability** (CWE-290) exists in litellm. Attackers reach the vulnerable code path via ``request.url.path`` without authentication.
📍 Affected scope
litellm — . Attack surface: `request.url.path` / `Host` / `server_name`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.84.0**.
🛡️ Workaround
Workaround: If upgrading is not immediately possible, place the proxy behind an upstream component that validates or normalizes the `Host` header before forwarding (a CDN/WAF, a reverse proxy with explicit `server_name` allowlists, or a cloud load balancer with
🔍 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

  1. 1
    Identify exposure identify 
    grep -r 'litellm' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `litellm` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate 
    If upgrading is not immediately possible, place the proxy behind an upstream component that validates or normalizes the `Host` header before forwarding (a CDN/WAF, a reverse proxy with explicit `server_name` allowlists, or a cloud load balancer with

    パッチが適用されるまでの応急処置として、If upgrading is not immediately possible, place the proxy behind an upstream component that validates or normalizes the `Host` header before forwarding (a CDN/WAF, a reverse proxy with explicit `server_name` allowlists, or a cloud load balancer with を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade litellm to 1.84.0

    ステージング環境で 1.84.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-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"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →