Categories
CVE-2026-59820 medium CVSS 6.5

Path Traversal in litellm (CVE-2026-59820)

Summary

Path traversal in litellm (CVE-2026-59820). Data can be tampered with by attackers. Exploitable via POST /v1/skills. Mitigation: upgrade to 1.83.7-stable or later.

Original description

The description as published by the source.

Impact

LiteLLM Skills archive extraction did not sufficiently validate file paths from uploaded skill ZIP archives. An authenticated user with access to LiteLLM LLM API routes, or a key whose allowed_routes includes /v1/skills, anthropic_routes, or llm_api_routes, could upload a crafted skill archive containing path traversal entries.

When the skill was processed for execution, those entries could be written outside the intended extraction/staging directory. This could allow arbitrary file write and may lead to code execution depending on deployment configuration and writable paths.

Patches

The issue is fixed in 1.83.7-stable.

LiteLLM recommens upgrading to 1.83.7-stable or later.

Workarounds

If upgrading is not immediately possible:

  1. Block POST /v1/skills at your reverse proxy or API gateway.
  2. Restrict Skills API access to trusted users only.

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-59820 has been found in litellm.
Attackers can target a specific entry point like POST /v1/skills over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade litellm to 1.83.7-stable or later.
If unsure, ask your IT team or search "litellm CVE-2026-59820" on the vendor's site.

CVE-2026-59820 (litellm) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /v1/skills / allowed_routes / anthropic_routes / llm_api_routes
Patched: 1.83.7-stable — apply immediately
Workaround: 1. Block POST /v1/skills 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

Path traversal (CWE-22) exists in litellm. Attackers reach the vulnerable code path via POST /v1/skills.

📍 Affected scope

Check the vendor advisory for the affected versions of litellm. Attack surface: POST /v1/skills / allowed_routes / anthropic_routes / llm_api_routes.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.83.7-stable.

🛡️ Workaround

Workaround: 1. Block POST /v1/skills at your reverse proxy or API gateway.

🔍 Detection

Search webserver/proxy logs for unusual POST /v1/skills requests with malformed payloads or SQL meta-characters. 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

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

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

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /v1/skills' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /v1/skills への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply temporary workaround mitigate
    1. Block `POST /v1/skills` at your reverse proxy or API gateway.

    パッチが適用されるまでの応急処置として、1. Block POST /v1/skills at your reverse proxy or API gateway. を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 4
    Apply patch patch
    Upgrade litellm to 1.83.7-stable

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

  5. 5
    Post-deployment verification verify
    Replay attack against POST /v1/skills on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip litellm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.83.7"}]}]
PyPI litellm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.83.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details