deepset
Vulnerability disclosure program on Self-hosted deepset.ai
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
While we do not operate a formal bug bounty program at this point in time, we do appreciate the time and skill that goes into responsible security research, and we are happy to work with researchers who report valid findings in good faith.
- Response
-
Within 5 days
Acknowledging receipt of your report within 5 business days.
- Safe harbor
-
Full
We will not take adverse action against researchers who follow this policy.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 3 excluded.
Source code 2
- Haystack open-source framework
- https://github.com/deepset-ai/haystack/blob/main/SECURITY.md No bounty
Domains 1
- deepset.ai
Web 1
- deepset.ai and all subdomains
Wildcard domains 1
- *.deepset.ai No bounty
Products and areas 1
- Haystack Enterprise Platform
Out of scope (3)
- Non-production environments, unless the finding demonstrates exploitable lateral movement from a non-production environment into production infrastructure
- Third-party services or integrations hosted by other providers
- Vulnerabilities in upstream open-source dependencies not maintained by deepset
Rules
What the policy asks of you, and the bug types it won't reward, quoted from deepset's policy. "We" in these lines means the program, not this site.
While testing
-
Report vulnerabilities to us before disclosing them publicly or to any third party.
-
Allow us a reasonable period (90 days) to investigate and remediate the issue before any public disclosure.
-
Do not access, modify, or delete data belonging to other users or accounts you do not own.
-
Do not degrade or disrupt our services or infrastructure.
-
Do not exploit a vulnerability beyond what is necessary to confirm it exists.
-
Act in good faith and comply with all applicable laws.
Not accepted
-
TLS configuration weaknesses (e.g., support for older cipher suites, TLS 1.0, SWEET32)
-
Social engineering or phishing attacks targeting deepset employees or contractors
-
Denial-of-service (DoS) or distributed denial-of-service (DDoS) attacks
-
Brute-force attacks against authentication or login systems
-
Attacks against deepset's physical infrastructure
-
Clickjacking on pages with no sensitive actions
-
Self-XSS that cannot be used to exploit other users
-
Missing cookie flags on non-sensitive cookies
-
Information disclosure that does not present a meaningful security risk (e.g., server version headers, stack traces on non-production environments)
-
Exposed public source maps (e.g., .map files that reveal readable JS source but do not expose secrets, credentials, or internal API logic)
-
Content spoofing or text injection without a demonstrable security impact
-
Reports generated by automated scanning tools (e.g., Nuclei, Burp Suite, Nessus, etc.) or AI without manual validation of an actual exploitable vulnerability
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope
− security.md
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.