LiteLLM vulnerable to server-side template injection in the /prompts/test endpoint
CVE-2026-37004 · GHSA-6wvf-77m9-58rm · published 2026-08-27 · updated 2026-09-08
- Severity
- Critical
- CVSS score
- 9.8
- Chance of exploitation (EPSS)
- 0.80%
- Fixed in
- 1.83.7
- Exploitation No known exploitation
- Automatable Yes
- Technical impact Total
- CISA SSVC
BerriAI litellm <=1.82.4 is vulnerable to Server-Side Template Injection (SSTI), which allows unauthenticated remote attackers to execute arbitrary OS commands via a crafted dotprompt_content parameter in the /prompts/test endpoint due to use of an unsandboxed jinja2.Environment.
Upgrade litellm to 1.83.7 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| litellm | PyPI | < 1.83.7 | 1.83.7 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- CriticalStorybook: Missing origin validation in Storybook preview allows code injection from malicious websites@storybook/addon-mcp, @storybook/addon-mcp
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMalicious code in litellm (PyPI)litellm, litellm, litellm
- CriticalLiteLLM: Authentication Bypass via Host Header Injectionlitellm
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.