Cyber Resilience

CVE-2023-1712

Deepset Haystack ≤ 2023-03-29

Public PoC
Published
30 March 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0084 55th percentile
Risk Priority 73 floored blend · peak EPSS

Summary

CVE-2023-1712 is a critical-severity Use of Hard-coded, Security-relevant Constants (CWE-547) vulnerability in Deepset Haystack. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 45% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as NLP and Transformers.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Use of Hard-coded, Security-relevant Constants in GitHub repository deepset-ai/haystack prior to 0.1.30.

CWE(s)

AI Security AnalysisAI

AI Category
NLP and Transformers
Risk Domain
N/A
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: ai

Related Threats

CVEs Like This One

CVE-2025-49151Shared CWE-547
CVE-2024-41885Shared CWE-547
CVE-2025-2079Shared CWE-547
CVE-2024-32021Shared CWE-547
CVE-2026-28256Shared CWE-547
CVE-2025-2081Shared CWE-547
CVE-2025-23253Shared CWE-547
CVE-2024-39888Shared CWE-547
CVE-2025-30206Shared CWE-547

Affected Assets

deepset
haystack
≤ 2023-03-29

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce use of named constants and configurable values for security parameters.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure SDLC processes can catch hard-coded constants during reviews and testing.

prevents

Secure coding standards explicitly prohibit hard-coded security constants.

none

Change management may detect constant changes but does not prevent their initial hard-coding.

none

Configuration management can externalize constants but does not directly address coding practice.

References