Insecure Jinja2 templates rendered in Haystack Components can lead to RCE
CVE-2024-41950 · GHSA-hx9v-6r9f-w677 · published 2024-07-31
- Severity
- High
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- 1.2%
- Fixed in
- 2.3.1
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
Haystack clients that let their users create and run Pipelines from scratch are vulnerable to remote code executions. Certain Components in Haystack use Jinja2 templates, if anyone can create and render that template on the client machine they run any code.
Upgrade haystack-ai to 2.3.1 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.
The problem has been fixed with PRs deepset-ai/haystack#8095 and deepset-ai/haystack#8096. Both have been released with Haystack 2.3.1.
Prevent users from running the affected Components, or only let users use preselected templates.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| haystack-ai | PyPI | < 2.3.1 | 2.3.1 |
- 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
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- 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
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.