- Top reward
- $100
- Top severity paid
- Not published
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $100
- top reward.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 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.
The policy page has no reward table. Here is what it says, in its own words.
- Top reward
-
$100
Typical rewards are bounties of up to 100 USD for low severity vulnerabilities, with higher bounty amounts for more severe issues.
- Response
-
Within 3 days
To respond to your report within 3 business days.
- Safe harbor
-
Full
If you followed the instructions above, we will not take legal action against you in regard to your report.
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, 4 excluded.
Domains 4
- datachain.ai
- docs.datachain.ai
- responsibledisclosure.nl
- studio.datachain.ai
Source code 2
- https://github.com/datachain-ai/datachain
- Open Source tools - for critical findings only ( details ), including but not limited to the datachain library
Out of scope (4)
- datachain-ai.slack.com
- github.com/datachain-ai
- Third-party systems and services that are not part of our tools' dependencies / supply chain
- Vulnerabilities in third-party services or platforms used to maintain and build DataChain software
Rules
What the policy asks of you, and the bug types it won't reward, quoted from DataChain's policy. "We" in these lines means the program, not this site.
While testing
-
Email your findings to [email protected] .
-
Provide sufficient information to reproduce the problem.
-
Do not take advantage of the vulnerability or breach you have discovered.
-
Do not disclose the bug/vulnerability to others until it has been resolved by us and confirmed.
-
please do not attempt to carry out DoS attacks, leverage black hat SEO techniques, spam people, employ social engineering
-
Whenever possible, please try to test the vulnerabilities locally without impacting other users.
-
If you have created a Studio account for security research purposes, please send us the account name and email you used.
-
please send your bug reports directly to the owner of the vulnerable package first and ensure that the issue is addressed upstream
-
Be shared no earlier than 90 days after the issue was fixed & released upstream
Not accepted
-
HTTPS configuration, including supported TLS versions & cipher suites
-
DNS records including those related to email (SPF, DKIM, DMARC) and certificate issuance (CAA)
-
Are unconfirmed reports from automatic vulnerability scanners.
-
Are related to rate limits or brute force attacks.
-
Only demonstrate the ability to infer versions of software that we run (banner grabbing).
-
Are found in services that are out of scope .
-
Are found in our open source tools and are of low severity.
-
Are already known to us.
-
Have negligible security impact or cannot be proven to be exploitable.
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.
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.