- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 3
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 1 day
- 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.
- Pays cash
-
Yes
The available reward options include financial rewards, free licenses for JetBrains products, and mentioning a reporter in the JetBrains Security Bulletin .
- Response
-
Within 1 days
24 hours from receiving the report
- Safe harbor
-
Partial
All communication and disclosure should be made in a coordinated manner, not putting our business or our users and customers at risk.
- Hall of fame
-
Yes
mentioning a reporter in the JetBrains Security Bulletin
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
3 assets you may test.
Domains 1
- www.jetbrains.com/legal/websites
Products and areas 2
- JetBrains products
- JetBrains websites
Rules
What the policy asks of you, and the bug types it won't reward, quoted from JetBrains's policy. "We" in these lines means the program, not this site.
While testing
-
All communication and disclosure should be made in a coordinated manner, not putting our business or our users and customers at risk.
-
A report should include clear reproduction steps, a working PoC where applicable, and evidence of real security impact.
-
Reports generated using AI-based tools should be reviewed and manually validated before submission.
-
There should not be any attacks that attempt to access JetBrains or our customers' confidential data.
-
There should not be any attacks that lead to denial of service attacks on our systems and services or jeopardizing them in any way.
-
No automated tools should be used for attacking our systems or services.
-
No social engineering should be targeted against JetBrains employees or customers.
-
Proof of concept should be drafted using your data when possible.
-
The impact from the demonstration should be limited to the necessary minimum required to prove the concept.
Not accepted
-
Reports based only on theoretical scenarios, assumptions, or unverified scanner output may be closed without further investigation.
-
The issue should not already have been announced publicly or known by JetBrains.
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 6 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.