Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-40217 high CVSS 8.8

Vulnerability in litellm (CVE-2026-40217)

Summary

Vulnerability in litellm (CVE-2026-40217). Successful exploitation can lead to full system takeover. Exploitable via POST /guardrails/test_custom_code. Mitigation: upgrade to 1.83.10 or later.

Original description

The description as published by the source.

Impact

The POST /guardrails/test_custom_code endpoint runs user-supplied Python inside a hand-rolled sandbox. The sandbox can be escaped using bytecode-level techniques, allowing arbitrary code execution in the proxy process — which runs as root in the default Docker image.

Reaching the endpoint requires a proxy-admin credential in default configurations.

Patches

Fixed in 1.83.11. The hand-rolled sandbox has been replaced with RestrictedPython. Upgrade to 1.83.11 or later.

Workarounds

If upgrading is not immediately possible, block POST /guardrails/test_custom_code at your reverse proxy or API gateway.

References

Source: GitHub Security Advisories (Global) 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-40217 has been found in litellm.
Attackers can target a specific entry point like POST /guardrails/test_custom_code over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade litellm to 1.83.10 or later.
If unsure, ask your IT team or search "litellm CVE-2026-40217" on the vendor's site.

CVE-2026-40217 (litellm) — CWE-420 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /guardrails/test_custom_code / RestrictedPython
Patched: 1.83.10 — apply immediately
Workaround: If upgrading is not immediately possible, block POST /guardrails/test_custom_code 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

A vulnerability (CWE-420) exists in litellm. Attackers reach the vulnerable code path via POST /guardrails/test_custom_code.

📍 Affected scope

Check the vendor advisory for the affected versions of litellm. Attack surface: POST /guardrails/test_custom_code / RestrictedPython.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.83.10.

🛡️ Workaround

Workaround: If upgrading is not immediately possible, block POST /guardrails/test_custom_code at your reverse proxy or API gateway.

🔍 Detection

Search webserver/proxy logs for unusual POST /guardrails/test_custom_code 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 /guardrails/test_custom_code' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply temporary workaround mitigate 
    If upgrading is not immediately possible, block `POST /guardrails/test_custom_code` at your reverse proxy or API gateway.

    パッチが適用されるまでの応急処置として、If upgrading is not immediately possible, block POST /guardrails/test_custom_code at your reverse proxy or API gateway. を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 4
    Apply patch patch 
    Upgrade litellm to 1.83.10

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

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

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

Affected packages

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

References

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