CVE-2026-42271

HIGHNVD 8.89.0
EchelonGraph scoreHIGH confidence

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_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
8.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 80%CVSS: 8.8Exploit: NoneExposed: 0

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.0(high)
EPSS
99.6%
KEV
⚠ Exploited

Published

May 8, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated May 8, 2026
Patch available. Sources: github.
github Patch Available

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

https://github.com/BerriAI/litellm/security/advisories/GHSA-v4p8-mg3p-g94g
generic

Release v1.83.7-stable · BerriAI/litellm · GitHub

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

Patch Availability(3)

Vendor / EcosystemFixed in / 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 rangeFixed inDependents
litellm1.74.12 ... 1.83.6 (107 versions)1.83.7

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 92× in last 7d / 357× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 465 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCamnsecurity/CVE-2026-42271-LiteLLM-RCE
    First seen 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
    First seen Jan 1, 2026

    LiteLLM - Command Injection

    Open source ↗

Frequently asked(6)

What is CVE-2026-42271?
CVE-2026-42271 is a high vulnerability 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 CVE-2026-42271 disclosed?
CVE-2026-42271 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 patching attention.
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.
Which products are affected by CVE-2026-42271?
CVE-2026-42271 affects BerriAI LiteLLM. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2026-42271?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42271, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.