CVE Intelligence
CISA KEV High Injection

CVE-2026-42271 — BerriAI LiteLLM Command Injection Vulnerability

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.

Published May 8, 2026 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Jun 8, 2026 Detection templates (Nuclei) · 1Metasploit modules · 1Proofs of concept on GitHub · 2
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (nuclei, metasploit, github)+20
  • EPSS 92.6% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Jun 8, 2026
EPSS FIRST
92.57%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
BerriAI
Litellm and 1 more
CVSS base
8.8
High · 5 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Pip Litellm: fixed in version 1.83.7 — github.com (GitHub Security Advisories)

CISA required action CISA

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

US federal deadline: Jun 22, 2026 — passed 115 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (BerriAI Litellm, Litellm Litellm, Red Hat Openshift Ai…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
BerriAI Litellm version >= 1.74.2, < 1.83.7 Vulnerable CVE Program (cve.org) e CISA ADP
Litellm Litellm ≥ 1.74.2 and < 1.83.7 Vulnerable NIST National Vulnerability Database
Red Hat Openshift Ai ≥ 2.25 and < 2.25.8≥ 3.3 and < 3.3.4version 3.4 Vulnerable NIST National Vulnerability Database
Pip Litellm ≥ 1.74.2 and < 1.83.7 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.7 CVSS 4.0 High — — security-advisories@github.com via NIST National Vulnerability Database
8.7 CVSS 4.0 High — — GitHub_M via CVE Program (cve.org) e CISA ADP
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.8 CVSS 3.1 High 2.8 5.9 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-77 · Command Injection

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Jun 8, 2026
Federal deadline
Jun 22, 2026
passed 115 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Detection templates (Nuclei)
Metasploit modules
Proofs of concept on GitHub

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 92.57%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
  • Hunt retroactively in logs from before Jun 8, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · pip/litellm
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · berriai/litellm
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · litellm/litellm, redhat/openshift ai
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    Jun 7, 2026 · CISA
  • CVE published
    May 8, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

11 on the record

Elsewhere on this site

BerriAI
every CVE for this vendor
2026-06
what else CISA listed that month
Injection
same class
CWE-77
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-108575 BerriAI LiteLLM Secret Resolution main.py get_secret improper authorization 4d
  • CVE-2026-108574 BerriAI LiteLLM Spend Tracking spend_management_endpoints.py ui_view_session_spend_logs authorization 4d
  • CVE-2026-59821 LiteLLM: Custom Code Guardrails production endpoints bypass code safety checks Jul 8, 2026
  • CVE-2026-59820 LiteLLM: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') Jul 8, 2026
  • CVE-2026-59819 LiteLLM: Local file read via request-supplied OIDC file references Jul 8, 2026
  • CVE-2026-59822 BerriAI LiteLLM Improper Authentication Vulnerability KEV Jul 8, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-42271 is "BerriAI LiteLLM Command Injection Vulnerability", rated High. It affects Litellm (BerriAI); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 92.57% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.