Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

Use of hard-coded, security-relevant constants in deepset-ai/haystack

CVE-2023-1712GHSA-w7qg-j435-78qw

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI farm-haystack

    Affected
    <= 1.15.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2023-1712: 0.85% estimated exploitation activity in the next 30 days; percentile 58.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Use of Hard-coded, Security-relevant Constants in GitHub repository deepset-ai/haystack in version 1.15.0 and prior. A patch is available at commit 5fc84904f198de661d5b933fde756aa922bf09f1.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from osv record GHSA-w7qg-j435-78qw

  2. Revision 3 · amended ·

    Amended from ghsa record GHSA-w7qg-j435-78qw

  3. Revision 2 · amended ·

    Amended from ghsa record GHSA-w7qg-j435-78qw

  4. Revision 1 · created ·

    Published from osv record GHSA-w7qg-j435-78qw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-1712

Advisory: Use of hard-coded, security-relevant constants in deepset-ai/haystack
IDs: CVE-2023-1712, GHSA-w7qg-j435-78qw
Record: https://patchnext.com/advisories/cve-2023-1712 (revision 4, source checked 28 Oct 2026, 06:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI farm-haystack: affected <= 1.15.0

## Suggested inspection (read-only)
- `python -m pip show farm-haystack`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on farm-haystack.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w7qg-j435-78qw (OSV record GHSA-w7qg-j435-78qw lists affected ranges: PyPI farm-haystack >=0 <=1.15.0)
- Verified: https://github.com/advisories/GHSA-w7qg-j435-78qw (GitHub-reviewed advisory GHSA-w7qg-j435-78qw lists affected ranges: PyPI farm-haystack >=0 <=1.15.0)

Commands are suggestions: review each one before running it.

Loading voting…