What is CVE-2024-41950?

CVE-2024-41950 is a high-severity security vulnerability in haystack-ai (pip), affecting versions < 2.3.1. It is fixed in 2.3.1.

How severe is CVE-2024-41950?

CVE-2024-41950 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of haystack-ai are affected by CVE-2024-41950?

haystack-ai (pip) versions < 2.3.1 is affected.

Is there a fix for CVE-2024-41950?

Yes. CVE-2024-41950 is fixed in 2.3.1. Upgrade to this version or later.

Is CVE-2024-41950 exploitable, and should I be worried?

Whether CVE-2024-41950 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-41950 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-41950?

Upgrade haystack-ai to 2.3.1 or later.

CVE-2024-41950 in haystack-ai

Q: How severe is CVE-2024-41950?

CVE-2024-41950 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of haystack-ai are affected by CVE-2024-41950?

haystack-ai (pip) versions < 2.3.1 is affected.

Q: Is there a fix for CVE-2024-41950?

Yes. CVE-2024-41950 is fixed in 2.3.1. Upgrade to this version or later.

Q: Is CVE-2024-41950 exploitable, and should I be worried?

Whether CVE-2024-41950 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-41950 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-41950?

Upgrade haystack-ai to 2.3.1 or later.

Summary

Insecure Jinja2 templates rendered in Haystack Components can lead to RCE

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.

CVE-2024-41950 has a CVSS score of 7.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.1); upgrading removes the vulnerable code path.

Affected versions

haystack-ai (< 2.3.1)

Security releases

haystack-ai → 2.3.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2024-41950? CVE-2024-41950 is a high-severity security vulnerability in haystack-ai (pip), affecting versions < 2.3.1. It is fixed in 2.3.1.
How severe is CVE-2024-41950? CVE-2024-41950 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of haystack-ai are affected by CVE-2024-41950? haystack-ai (pip) versions < 2.3.1 is affected.
Is there a fix for CVE-2024-41950? Yes. CVE-2024-41950 is fixed in 2.3.1. Upgrade to this version or later.
Is CVE-2024-41950 exploitable, and should I be worried? Whether CVE-2024-41950 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-41950 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-41950? Upgrade haystack-ai to 2.3.1 or later.