← Back to Vulnerability Reports CVE Intelligence

CVE-2026-42271

BerriAI LiteLLM•HIGH · CVSS 8.8• In the wild In CISA KEV

What is 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.

CVSS8.8 NVD 3.1
SeverityHIGH
Exploitation In the wild In CISA KEV
EPSS93% · P100
Triage statusActive Exploit
ActionPatch immediately
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWECWE-77, CWE-78
NVD published2026-05-08
NVD last modified2026-07-15

Timeline

  • 2026-05-08Published to the U.S. National Vulnerability Database (NVD)
  • 2026-06-08Added to the CISA Known Exploited Vulnerabilities (KEV) catalog
  • 2026-06-22CISA federal remediation deadline (BOD 22-01)
  • 2026-07-15NVD record last updated
  • 2026-10-08First covered in a defend.network daily briefing

CISA Known Exploited Vulnerability

BerriAI LiteLLM Command Injection Vulnerability

Added to KEV2026-06-08
Federal patch deadline2026-06-22
Known ransomware useUnknown

Affected product

BerriAI LiteLLM

NVD also lists CPE entries for: Litellm, Redhat Openshift Ai

Remediation Steps

  1. Apply the vendor security update for Litellm as a priority.
  2. Restrict network exposure of the affected service to trusted sources until patched.
  3. Review logs and detections for indicators of exploitation.
  4. Confirm fixed versions against the official vendor advisory before deploying.

Related vulnerabilities

Browse all tracked CVEs in the defend.network CVE database →

🤖 This CVE page is generated by defend.network from NVD, CISA KEV, EPSS, and our verified daily briefings. Severity and exploitation data come from official sources; always verify remediation steps against the official vendor advisory before acting in production.