- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
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]
- Partial safe harbor
- Some legal protection; read the terms.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
We are a small distributed team which means we are unable to offer financial rewards for reporting vulnerabilities at this stage.
- Safe harbor
-
Partial
Do not leverage the existence of a vulnerability or access to personal data or sensitive information to make threats or extortionate demands.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test.
Domains 1
- gitbook.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from GitBook's policy. "We" in these lines means the program, not this site.
While testing
-
Your submission must include a working Reproduction Guide to be considered for a reward.
-
If you encounter any personal data or sensitive information in the course of your research, stop and notify our team immediately
-
Do not save, copy, download, transfer, disclose, or otherwise use this data.
-
Do not degrade, interrupt, or deny services to our users or take any actions that can affect the availability or integrity of GitBook's systems and data
-
Do not incur a loss of funds that are not your own.
-
Your research must not violate any applicable laws or regulations.
-
must be at least 18 years old.
Not accepted
-
Denial of service
-
Disclosure of server or software version numbers
-
Hypothetical subdomain takeovers without supporting evidence
-
Issues that are premised on unlikely user interaction
-
Missing best practices in SSL/TLS configuration
-
Missing email best practices
-
Missing HttpOnly or Secure flags on cookies
-
Previously known vulnerable libraries without a working Proof-of-Concept
-
Rate limiting or brute force issues on non-authentication endpoints
-
Reports exploiting the behavior of, or vulnerabilities in, outdated browsers
-
Reports of spam
-
Social engineering
-
Tabnabbing
-
Unconfirmed reports from automated vulnerability scanners
-
Attacks requiring MITM or physical access to a user's device
-
Best practice reports without a valid exploit
-
Clickjacking on pages with no sensitive actions
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
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 2 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.