CVE-2026-30623: litellm · Command Injection
Affects litellmSource CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 4.9% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Jul 2026
Detectable: evidence found.
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubberriai/litellmpkg:github/berriai/litellmOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official fix is available, avoid deploying LiteLLM version 1.18.10 in untrusted environments or restrict access to the MCP server creation functionality. Monitor vendor communications for updates and apply patches promptly once released.
Description
LiteLLM version 1.18.10 contains a critical remote code execution vulnerability in its MCP server creation functionality. The vulnerability arises because the application executes arbitrary commands and arguments specified in a JSON configuration without validation. This allows an attacker to run operating system commands with the privileges of the LiteLLM process. The vulnerability has a CVSS score of 9.8, indicating a critical severity level. No patch or official remediation has been confirmed at this time.