- Top reward
- $5,000
- Top severity paid
- Critical
- Assets in scope
- 13
- Public CVEs
- 2
- Last change
At a glance
What to know before you start testing.
- Pays up to $5,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- 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 HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$5,000 |
| High |
|
$2,000 |
| Medium |
|
$250 |
| Low |
|
$100 |
- Response
-
Within 3 days
Time to first response (from report submit) - 3 business days
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
13 assets you may test.
Web 2
- calendar.notion.so Critical
- mail.notion.so Critical
Android apps 1
- notion.id Critical
Desktop and binaries 1
- Notion Desktop App Critical
Products and areas 9
- Github Repositories or other public artifacts owned by makenotion Critical
- Notion AI Critical
- Notion Authentication Critical
- Notion Frontend Critical
- Notion Integrations Critical
- Notion MCP Critical
- Privilege Escalation Critical
- Product API Critical
- Public API Critical
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Notion Labs, Inc. (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
-
Only interact with accounts you own or with the explicit permission of the account holder.
-
Testing on any accounts containing production data.
-
Accounts should be created specifically for the purpose of the engagement.
-
Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
Not accepted
-
Social engineering or phishing of Notion employees or contractors
-
Any attacks against Notion's physical property or data centers
-
Any attacks against Notion's users
-
Use of automated scanning tools
-
Lack of rate limiting on any resources
-
Password policy issues, including lack of upper limit on passwords
-
HTTP 404 or other error codes and pages
-
Banner or version disclosure of any kind
-
Presence of common public files, such as robots.txt or files in the .well-known directory
-
Self-XSS issues
-
Spamming
-
Clickjacking on pages with no sensitive actions
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Missing best practices in Content Security Policy.
-
Missing HttpOnly or Secure flags on cookies
-
Tabnabbing
-
Open redirect - unless an additional security impact can be demonstrated
-
Notion hosting malware / Spam / Phishing websites
-
Issues that require unlikely user interaction
-
Obtaining access to a paid feature of a higher level plan
-
Bypasses of lock features on page and database views
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 44 minutes 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 added
Notion MCP
-
Scope added
calendar.notion.so
-
Scope added
Github Repositories or other public artifacts owned by makenotion
-
Scope added
mail.notion.so
-
Scope added
Notion AI
-
Scope added
Notion Authentication
-
Scope added
Notion Desktop App
-
Scope added
Notion Frontend
-
Scope added
Notion Integrations
-
Scope added
notion.id
-
Scope added
Privilege Escalation
-
Scope added
Product API
-
Scope added
Public API
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2024-23745 | In Notion Web Clipper 1.0.3(7), a .nib file is susceptible to the Dirty NIB attack. NIB files can be manipulated to execute arbitrary commands. Additionally, even if a NIB file is modified within an application, Gatekeeper may still permit the execution of the application, enabling the execution of arbitrary commands within the application's context. NOTE: the vendor's perspective is that this is | Critical 9.8 | 31 Jan 2024 |
| CVE-2024-23743 | Notion through 3.1.0 on macOS might allow code execution because of RunAsNode and enableNodeClilnspectArguments. NOTE: the vendor states "the attacker must launch the Notion Desktop application with nonstandard flags that turn the Electron-based application into a Node.js execution environment." | Low 3.3 | 28 Jan 2024 |
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Notion Labs, Inc. looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.
Response Targets
Notion Labs, Inc. will make a best effort to meet the following response targets for hackers participating in our program:
- Time to first response (from report submit) - 3 business days
- Time to triage (from report submit) - 10 business days
- Time to resolution (from report submit) - Varies depending on severity
We’ll try to keep you informed about our progress throughout the process. Feel comfortable reaching out with any questions.
Disclosure Policy
- Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
Program Rules
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
- Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.
- Reports that cover more than one asset in scope will be paid out once at the highest paying in scope asset category.
Test Plan
Our application is self-sign up through Notion.so. Our Mobile apps are available through Apple and Android stores.
We strongly recommend using your HackerOne username and email as the account you're testing with.
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
Notion does not accept vulnerabilities in third-party services, unless specific mitigations from Notion are required to remediate the issue.
Note - Please use HackerOne mediation for any closed reports that you want to escalate. We do not accept requests to review closed reports at [email protected] or via Notion support under any circumstances.
The following potential issues are not considered in scope:
- Social engineering or phishing of Notion employees or contractors
- Any attacks against Notion's physical property or data centers
- Any attacks against Notion's users
- Use of automated scanning tools
- Lack of rate limiting on any resources
- Password policy issues, including lack of upper limit on passwords
- HTTP 404 or other error codes and pages
- Banner or version disclosure of any kind
- Presence of common public files, such as robots.txt or files in the .well-known directory
- Self-XSS issues
- Spamming
- Clickjacking on pages with no sensitive actions
- Clickjacking issues, unless an exploit showing account takeover or disclosure of sensitive resources is provided
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Comma Separated Values (CSV) injection without demonstrating a vulnerability.
- Missing best practices in SSL/TLS configuration.
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Rate limiting or bruteforce issues on non-authentication endpoints
- Missing best practices in Content Security Policy.
- Missing HttpOnly or Secure flags on cookies
- Missing security headers which don’t directly lead to a vulnerability or account compromise
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
- Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
- Tabnabbing
- Open redirect - unless an additional security impact can be demonstrated
- Notion hosting malware / Spam / Phishing websites
- Issues that require unlikely user interaction
- Obtaining access to a paid feature of a higher level plan
- Revealing identity information on published *.notion.site pages
- Expected behaviors as described in the Notion Documentation
- Javascript execution on file.notion.so and notion-static.com is expected. To be considered in scope, you will need to demonstrate how it harms users on in-scope assets.
- For Notion’s AI, engineered prompts to evoke inappropriate responses from the AI is out of scope. The usage of obfuscated or invisible characters to alter AI responses is in scope if security impact can be demonstrated. Reports regarding prompt injection must demonstrate security impact, e.g. data leaked outside of the workspace.
- Bypasses of lock features on page and database views
- The In-App Contact Us form is out of scope
- Denial of Service, stress tests, and other assessment that may be disruptive to Notion as a product or its operations
- Providing source code or debugging access
- Testing on any accounts containing production data. Testing on accounts not controlled by the party conducting or directing the testing. Accounts should be created specifically for the purpose of the engagement. Testing on accounts outside of those created for the purpose of the assessment is expressly prohibited. If cross org or cross workspace testing is performed, testers must use workspaces created for the purpose of the engagement.
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep Notion Labs, Inc. and our users safe!