PatchTheCVECVE-2023-1712: Use of Hard-coded, Security-relevant Constants in GitHub repository deepset-ai/haystack prior to 0.1.30.
CVE-2023-1712 is a critical-severity flaw (CVSS 9.8) affecting haystack. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Use of Hard-coded, Security-relevant Constants in GitHub repository deepset-ai/haystack prior to 0.1.30.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.9% (top 42%) |
| CISA exploited list | No |
| Weakness | CWE-547 |
| Published | 2023-03-30 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-1712?
haystack: upgrade to 2023-03-29. Exact commands for each OS are on this page.
Is CVE-2023-1712 being exploited?
CVE-2023-1712 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-1712 affect?
CVE-2023-1712 affects haystack. Severity is critical (CVSS 9.8). Use of Hard-coded, Security-relevant Constants in GitHub repository deepset-ai/haystack prior to 0.1.30.
How urgent is CVE-2023-1712?
Priority 59/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action