Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

LiteLLM MCP Test Command Execution (CVE-2026-42271)

CVE-2026-42271 is a LiteLLM command execution flaw in its MCP server test functionality.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
4 min read
CVE ID
CVE-2026-42271
Vendor
BerriAI
Affected Product
LiteLLM
Exploitation
Listed in CISA KEV
Published
2026-05-08

BerriAI says a valid proxy API key, including a low privilege internal user key, could reach the affected functionality. The proxy then ran a supplied command with its own process privileges.The vendor fixed the flaw in LiteLLM 1.83.7. CISA added the CVE to its Known Exploited Vulnerabilities catalog on 8 June 2026. That listing establishes exploitation of this CVE, but it does not identify which authentication path was used in each incident.

What it allows

How Does CVE-2026-42271 Work?

The vendor says LiteLLM's MCP test functionality accepted a server configuration and started its stdio command on the proxy host. Access required a valid proxy API key, but the functionality lacked an administrator role check. A low privilege key holder could therefore run commands with the proxy process privileges.

Horizon3 separately validated a chain with Starlette CVE-2026-48710. That Starlette flaw can make security checks see a different request path when an application relies on the reconstructed URL. Horizon3 says the chain removes the key requirement only when the LiteLLM deployment also includes affected Starlette and permits the bypass. This conditional remote code execution path belongs in a vulnerability intelligence platform with its separate exposure conditions.

Is CVE-2026-42271 Exploited?

CISA listed CVE-2026-42271 in KEV on 8 June 2026. Its catalog entry names the LiteLLM command injection flaw, without describing the Starlette chain or naming affected organizations. Horizon3 reports validation of the chain in its research environment; that validation does not show how every observed exploitation occurred.

Brandefense Blackhole counted seven dark chat posts mentioning CVE-2026-42271 from 18 August through 16 November 2026. It separately counted nine posts mentioning CVE-2026-48710 in the same period. These are posts, not incidents or installations; the sets may overlap and must not be added. A GitHub name search found two public repositories naming CVE-2026-42271; a repository name does not establish exploitation.

What Should Defenders Review?

Review proxy access records for unusual use of MCP test functionality and host telemetry for unexpected child processes. Horizon3 also recommends checking abnormal Host header activity when investigating the Starlette chain. Those observations warrant investigation; they are not standalone proof that this CVE was exploited.

Prioritize reachable, self hosted LiteLLM proxies that run an affected version and accept user keys. Record the running version, dependency version and exposure. Treat any suspected credential exposure as an incident response question because the proxy can hold model provider credentials.

Who is affected

Version Check

LiteLLM
Release LineAffected RangeFixed In
1.x1.74.2 to before 1.83.71.83.7
Release ranges source

For distribution packages and custom builds, check the supplier’s advisory.

The optional unauthenticated chain also depends on Starlette 1.0.0 or earlier and deployment-specific Host header handling; check those conditions separately.

Which LiteLLM Versions Are Affected by CVE-2026-42271?

BerriAI lists LiteLLM 1.74.2 through versions below 1.83.7 as affected; 1.83.7 is fixed. The standalone flaw requires access to the MCP test functionality with a valid proxy API key. An administrator role is not required on affected releases, so low privilege key holders matter.

Horizon3's authentication free chain additionally requires an affected Starlette dependency, version 1.0.0 or earlier, and an application path where its Host header flaw bypasses a security decision. The Starlette advisory says a fronting proxy can mitigate this path only if it rejects or normalizes malformed Host headers before forwarding. Verify the actual dependency tree and proxy behavior instead of assuming every LiteLLM deployment has the chain.

Upgrade LiteLLM to 1.83.7 or later and Starlette to 1.0.1 or later where the chain applies. Confirm the versions used by the running proxy after deployment, including container images or pinned dependencies. Until upgrade, BerriAI advises blocking the affected MCP test functionality at the reverse proxy or API gateway. Record the fix in your patch management process.

Timeline

  1. 2026-04-21

    BerriAI published the LiteLLM security advisory.

  2. 2026-05-08

    NVD published the CVE record; Horizon3 dates the LiteLLM 1.83.7 fix to this day.

  3. 2026-05-21

    The Starlette project published its advisory for CVE-2026-48710.

  4. 2026-06-01

    Horizon3 says its researchers validated the two flaw chain.

  5. 2026-06-08

    CISA added CVE-2026-42271 to its KEV catalog.

What to do

  1. Inventory the running proxy

    Find self hosted LiteLLM proxies and record the running version, accepted key types, network reachability, and installed Starlette version.

  2. Upgrade and verify both components

    Move affected LiteLLM releases to 1.83.7 or later. Where the chain applies, use Starlette 1.0.1 or later and verify both versions in the running deployment.

  3. Restrict exposure until the update

    BerriAI advises blocking the affected MCP test functionality at a reverse proxy or API gateway. Restrict access to trusted network segments while preparing the fix.

  4. Investigate suspicious activity

    Review unusual MCP test requests, unexpected proxy child processes, and abnormal Host header activity. If evidence suggests compromise, assess and rotate exposed model provider credentials.

What Brandefense can do

Frequently Asked Questions

Does CVE-2026-42271 require authentication?

By itself, the LiteLLM flaw requires a valid proxy API key, including a low privilege internal user key. Horizon3 validated an unauthenticated path only when it is chained with applicable Starlette CVE-2026-48710 conditions.

Which LiteLLM release fixes CVE-2026-42271?

BerriAI lists LiteLLM 1.83.7 as fixed. Check the running proxy version after the update, and check Starlette separately if the authentication bypass chain applies.

Does CISA KEV confirm the unauthenticated chain was used?

CISA lists exploitation of CVE-2026-42271, but its entry does not describe the access path. Horizon3 separately reports validating the chain in its research environment.

What should a team inspect after finding an affected proxy?

Review access records for unusual MCP test activity and host records for unexpected proxy child processes. Check abnormal Host header activity if the Starlette chain could apply.

Sources

  1. Authenticated Command Execution via MCP Stdio Test EndpointsBerriAI
  2. CVE-2026-42271 Chained with CVE-2026-48710Horizon3
  3. Missing Host Header Validation Poisons request.url.pathStarlette
  4. Known Exploited Vulnerabilities CatalogCISA
  5. CVE-2026-42271 DetailNVD
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →