Impact
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.
Patches
The problem has been fixed with PRs #8095 and #8096.
Both have been released with Haystack 2.3.1
.
Workarounds
Prevent users from running the affected Components, or only let users use preselected templates.
References
The list of impacted Components can be found in the release notes for 2.3.1
.
https://github.com/deepset-ai/haystack/releases/tag/v2.3.1
Impact
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.
Patches
The problem has been fixed with PRs #8095 and #8096.
Both have been released with Haystack
2.3.1
.Workarounds
Prevent users from running the affected Components, or only let users use preselected templates.
References
The list of impacted Components can be found in the release notes for
2.3.1
.https://github.com/deepset-ai/haystack/releases/tag/v2.3.1