RCE in Berriai Litellm

CVE-2026-42271

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.

Vulnerability class: Command Injection (OS Command Injection)

EPSS: 0.836 (99.7th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Affected products

Weakness classification (CWE)

CISA KEV (Known Exploited Vulnerabilities)

This CVE is on the CISA KEV catalog, added on . CISA KEV inclusion means CISA has confirmed in-the-wild exploitation; US federal agencies are required to remediate within a published due date.

BOD 22-01 due date: .

Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2026-42271?
CVE-2026-42271 is a high-severity vulnerability in Berriai Litellm, classified under Command Injection. CVSS score: 8.8/10. Published 2026-05-08.
How severe is CVE-2026-42271?
High severity. CVSS v3 base score is 8.8 out of 10.
Is CVE-2026-42271 known to be exploited?
Yes. CVE-2026-42271 is listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-06-08), indicating it is being actively exploited. 3 public proof-of-concept repositories are indexed.