CVE-2026-42271

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-06-08), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 93%CVSS: 8.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

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 v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
93%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA 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.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://github.com/BerriAI/litellm/security/advisories/GHSA-v4p8-mg3p-g94g · https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable · https://nvd.nist.gov/vuln/detail/CVE-2026-42271

Published

May 8, 2026

Last Modified

July 15, 2026

Advisory Details (9)

Auto-updated Oct 12, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: github_release, github, redhat, cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-42271
Red Hat

2467924 – (CVE-2026-42271) CVE-2026-42271 litellm: LiteLLM: Authenticated command execution via MCP stdio test endpoints

https://bugzilla.redhat.com/show_bug.cgi?id=2467924
Red HatMentions a patch (unverified)

CVE-2026-42271 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-42271
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:30056
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:28960
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:27784
GitHub advisoryMentions a patch (unverified)

Authenticated command execution via MCP stdio test endpoints · Advisory · BerriAI/litellm · GitHub

https://github.com/BerriAI/litellm/security/advisories/GHSA-v4p8-mg3p-g94g
GitHub release Patch Available

v1.83.7-stable

Patch available: BerriAI/litellm v1.83.7-stable

https://github.com/BerriAI/litellm/releases/tag/v1.83.7-stable

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17823100082026-06-25redhat
redhatrhoai/odh-llama-stack-core-rhel9:17818264062026-06-24redhat
redhatrhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:17816226272026-06-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
litellm1.74.12 ... 1.83.6 (107 versions)
  • 1.74.2 up to 1.83.7: fixed in 1.83.7
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 30× in last 7d / 199× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 871 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 771 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-16 11:49 UTCEG score recompute
  2. 2026-10-16 11:49 UTCVendor advisory
  3. 2026-10-15 12:34 UTCEG score recompute
  4. 2026-10-15 12:34 UTCVendor advisory
  5. 2026-10-14 16:33 UTCEPSS rescoreEPSS 93% · 99th percentile
  6. 2026-10-14 13:19 UTCEG score recompute
  7. 2026-10-14 13:19 UTCVendor advisory
  8. 2026-10-13 16:34 UTCEPSS rescoreEPSS 93% · 99th percentile
  9. 2026-10-13 14:04 UTCEG score recompute
  10. 2026-10-13 14:04 UTCVendor advisory
  11. 2026-10-12 16:34 UTCEPSS rescoreEPSS 93% · 99th percentile
  12. 2026-10-12 14:49 UTCEG score recompute
  13. 2026-10-12 14:49 UTCVendor advisory
  14. 2026-10-12 06:15 UTCVendor advisory
  15. 2026-10-12 02:15 UTCVendor advisory
  16. 2026-10-11 22:15 UTCVendor advisory
  17. 2026-10-11 19:49 UTCEG score recompute
  18. 2026-10-11 18:16 UTCVendor advisory
  19. 2026-10-11 17:03 UTCEG score recompute
  20. 2026-10-11 14:16 UTCEG score recompute
  21. 2026-10-11 14:16 UTCVendor advisory
  22. 2026-10-11 13:48 UTCEPSS rescoreEPSS 93% · 99th percentile
  23. 2026-10-11 10:19 UTCVendor advisory
  24. 2026-10-11 06:21 UTCVendor advisory
  25. 2026-10-11 02:21 UTCVendor advisory
Show 75 more
  1. 2026-10-10 22:21 UTCVendor advisory
  2. 2026-10-10 18:23 UTCVendor advisory
  3. 2026-10-10 14:25 UTCVendor advisory
  4. 2026-10-10 10:27 UTCVendor advisory
  5. 2026-10-10 06:29 UTCVendor advisory
  6. 2026-10-10 02:31 UTCVendor advisory
  7. 2026-10-09 22:33 UTCVendor advisory
  8. 2026-10-09 18:34 UTCVendor advisory
  9. 2026-10-09 14:36 UTCVendor advisory
  10. 2026-10-09 10:36 UTCVendor advisory
  11. 2026-10-09 06:37 UTCVendor advisory
  12. 2026-10-09 02:39 UTCVendor advisory
  13. 2026-10-08 22:41 UTCVendor advisory
  14. 2026-10-08 18:44 UTCVendor advisory
  15. 2026-10-08 14:46 UTCVendor advisory
  16. 2026-10-08 10:47 UTCVendor advisory
  17. 2026-10-08 06:49 UTCVendor advisory
  18. 2026-10-08 02:51 UTCVendor advisory
  19. 2026-10-07 22:54 UTCVendor advisory
  20. 2026-10-07 18:55 UTCVendor advisory
  21. 2026-10-07 14:58 UTCVendor advisory
  22. 2026-10-07 11:00 UTCVendor advisory
  23. 2026-10-07 07:03 UTCVendor advisory
  24. 2026-10-07 03:05 UTCVendor advisory
  25. 2026-10-06 23:07 UTCVendor advisory
  26. 2026-10-06 19:09 UTCEG score recompute
  27. 2026-10-06 19:09 UTCVendor advisory
  28. 2026-10-06 15:17 UTCEPSS rescoreEPSS 93% · 99th percentile
  29. 2026-10-06 15:12 UTCVendor advisory
  30. 2026-10-06 11:12 UTCVendor advisory
  31. 2026-10-06 07:15 UTCVendor advisory
  32. 2026-10-06 03:17 UTCVendor advisory
  33. 2026-10-06 03:17 UTCVendor advisory
  34. 2026-10-06 03:17 UTCVendor advisory
  35. 2026-10-05 23:18 UTCVendor advisory
  36. 2026-10-05 19:20 UTCVendor advisory
  37. 2026-10-05 15:21 UTCVendor advisory
  38. 2026-10-05 11:23 UTCVendor advisory
  39. 2026-10-05 07:26 UTCVendor advisory
  40. 2026-10-05 03:28 UTCVendor advisory
  41. 2026-10-04 23:31 UTCVendor advisory
  42. 2026-10-04 19:33 UTCVendor advisory
  43. 2026-10-04 15:36 UTCVendor advisory
  44. 2026-10-04 11:38 UTCVendor advisory
  45. 2026-10-04 07:41 UTCVendor advisory
  46. 2026-10-04 03:43 UTCVendor advisory
  47. 2026-10-03 23:46 UTCVendor advisory
  48. 2026-10-03 19:48 UTCVendor advisory
  49. 2026-10-03 15:50 UTCVendor advisory
  50. 2026-10-03 11:53 UTCVendor advisory
  51. 2026-10-03 07:55 UTCVendor advisory
  52. 2026-10-03 03:55 UTCVendor advisory
  53. 2026-10-02 23:55 UTCVendor advisory
  54. 2026-10-02 19:54 UTCVendor advisory
  55. 2026-10-02 15:56 UTCVendor advisory
  56. 2026-10-02 11:58 UTCVendor advisory
  57. 2026-10-02 07:57 UTCVendor advisory
  58. 2026-10-02 03:58 UTCVendor advisory
  59. 2026-10-02 00:00 UTCVendor advisory
  60. 2026-10-01 20:03 UTCVendor advisory
  61. 2026-10-01 16:06 UTCVendor advisory
  62. 2026-10-01 12:08 UTCVendor advisory
  63. 2026-10-01 08:10 UTCVendor advisory
  64. 2026-10-01 04:12 UTCVendor advisory
  65. 2026-10-01 00:15 UTCVendor advisory
  66. 2026-09-30 20:17 UTCVendor advisory
  67. 2026-09-30 16:20 UTCVendor advisory
  68. 2026-09-30 12:22 UTCVendor advisory
  69. 2026-09-30 08:24 UTCVendor advisory
  70. 2026-09-30 04:26 UTCVendor advisory
  71. 2026-09-30 00:28 UTCVendor advisory
  72. 2026-09-29 20:30 UTCVendor advisory
  73. 2026-09-29 16:32 UTCEG score recompute
  74. 2026-09-29 16:32 UTCVendor advisory
  75. 2026-09-29 12:32 UTCVendor advisory

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 GitHub PoC), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/multi/http/litellm_mcp_test_cmd_injection✓ verified
    Published Sep 28, 2026

    BerriAI LiteLLM Proxy MCP Test Endpoint Command Execution

    Open source ↗
  • GitHub PoCamnsecurity/CVE-2026-42271-LiteLLM-RCE
    Published Jul 7, 2026

    CVE-2026-42271 - LiteLLM AI Gateway MCP Command Injection RCE - PoC & Analysis | CVSS 8.8 | AMN SECURITY

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-42271.yaml
    Published Jun 3, 2026

    LiteLLM - Command Injection

    Open source ↗

Frequently asked(6)

What is CVE-2026-42271?
CVE-2026-42271 is a critical-severity vulnerability; its CVE record was published on May 8, 2026. 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…
When was the CVE record for CVE-2026-42271 published?
The CVE record for CVE-2026-42271 was published on May 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-42271 actively exploited?
Yes. CISA added CVE-2026-42271 to the Known Exploited Vulnerabilities catalog on June 8, 2026, affecting BerriAI LiteLLM. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2026-42271?
CVE-2026-42271 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2026-42271?
CVE-2026-42271 affects BerriAI LiteLLM. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2026-42271?
A fix for CVE-2026-42271 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42271 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42271

Explore →

Is Your Infrastructure Affected by CVE-2026-42271?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.