CVE-2026-105315: django-haystack · Eval Injection
Affects django-haystackSource CVE Database V5
Public exploit available · CVSS 5.1 Medium.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| django-haystack | Affected
| Fixed in– |
PyPIdjango-haystackpkg:pypi/django-haystackOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:django-haystack:django-haystack:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade django-haystack to version 3.4.0 or later, which includes the official fix for this vulnerability. No other mitigation is indicated or required as the patch fully addresses the issue.
Description
A vulnerability has been found in django-haystack up to 3.3.0. Affected is the function _to_python of the file haystack/backends/elasticsearch_backend.py of the component more_like_this Template Tag Handler. Such manipulation of the argument result_class leads to improper neutralization of directives in dynamically evaluated code. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 3.4.0 is able to address this issue. The name of the patch is eb05f193c9771a68dcc8cfac6674a0d48a52ee9d. It is suggested to upgrade the affected component.
References
- vuldb.com/vuln/413523 (opens in a new tab)
- vuldb.com/vuln/413523/cti (opens in a new tab)
- vuldb.com/cve/CVE-2026-105315 (opens in a new tab)
- vuldb.com/submit/978642 (opens in a new tab)
- github.com/django-haystack/django-haystack/security/advisories/GHSA-r3hx-x5rh-p9vv (opens in a new tab)
- github.com/django-haystack/django-haystack/commit/eb05f193c9771a68dcc8cfac6674a0d48a52ee9d (opens in a new tab)
- github.com/django-haystack/django-haystack/releases/tag/v3.4.0 (opens in a new tab)
- github.com/django-haystack/django-haystack/ (opens in a new tab)