Back to live map

CVE-2026-42271

KEVBerriAI LiteLLM Command Injection Vulnerability

BerriAI LiteLLM contains a command injection vulnerability that could allow any authenticated user, including holders of low-privilege internal-user keys, to run arbitrary commands on the host.

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. From version 1.74.2 to before version 1.83.7, two endpoints used to preview an MCP server before saving it - POST /mcp-rest/test/connection and POST /mcp-rest/test/tools/list - accepted a full server configuration in the request body, including the command, args, and env fields used by the stdio transport. When called with a stdio configuration, the endpoints attempted to connect, which spawned the supplied command as a subprocess on the proxy host with the privileges of the proxy process. The endpoints were gated only by a valid proxy API key, with no role check. Any authenticated user - including holders of low-privilege internal-user keys - could therefore run arbitrary commands on the host. This issue has been patched in version 1.83.7.

CVSS 4.0 vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
PublishedMay 8, 2026
Last modifiedJul 15, 2026
Added to KEVJun 8, 2026
Remediation dueJun 22, 2026
    83
    Risk assessment · Critical

    Actively exploited. Patch immediately.

    Exploitation
    Confirmed in the wild (CISA KEV)
    Federal remediation deadline
    Overdue by 126 days
    CVSS
    8.7 HIGH
    EPSS (30-day exploit probability)
    91.4% · top 1% of all CVEs
    Weakness
    CWE-77
    Attack vector
    Network, remotely reachable
    1. 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
    2. 2.Treat as emergency change: patch or isolate internet-facing instances first.
    3. 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
    4. 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

    Assessment is derived automatically from the live signals above; verify against your own asset inventory.