Security Program

Bug Bounty Program

Help us keep Octopus secure for everyone. Find vulnerabilities, report them responsibly, and earn rewards.

Rewards

What you can earn

We reward security researchers based on the severity and impact of their findings.

Cash Bounties

Up to $2,000 for critical vulnerabilities like RCE, auth bypass, or data leaks.

Swag Pack

Exclusive Octopus stickers, t-shirts, and limited-edition merch for valid reports.

Octopus Credits

Free usage credits on Octopus so you can review more PRs on us.

Recognition

Your name in our Hall of Fame, README, and a contributor badge on your profile.

Severity

Severity levels & rewards

Rewards scale with the impact of the vulnerability. Here is how we classify findings.

Critical

RCE, authentication bypass, mass data exposure, SQL injection

$500 - $2,000 + swag + credits

High

Stored XSS, IDOR, privilege escalation, API key leakage

$100 - $500 + swag + credits

Medium

CSRF, reflected XSS, information disclosure, open redirect

Swag + credits + recognition

Low

Minor misconfiguration, missing security headers, best practice violations

Recognition + sticker pack

Scope

What is in scope

Only test within the defined scope. Out-of-scope submissions will not be eligible for rewards.

In Scope
  • octopus-review.ai web application
  • Public API endpoints
  • GitHub & Bitbucket integration flows
  • Authentication & authorization flows
  • Octopus CLI tool
  • Webhook processing pipeline
Out of Scope
  • Denial of service (DoS/DDoS) attacks
  • Social engineering or phishing
  • Third-party services (Stripe, GitHub, etc.)
  • Spam or rate limiting without security impact
  • Issues in dependencies without a working exploit
  • Attacks requiring physical access
Rules

Rules of engagement

Follow these guidelines to ensure your research is authorized and eligible for rewards.

1

Give us 90 days to fix the issue before any public disclosure.

2

Only test against accounts you own. Do not access other users' data.

3

Do not use automated mass scanning tools that degrade service for others.

4

Submit reports through the designated channels listed below.

5

One vulnerability per report. Chaining is fine, but describe each step.

6

Do not publicly disclose the vulnerability before we confirm the fix.

7

Write your report in English with clear reproduction steps.

Recognition

Hall of Fame

Security researchers who helped make Octopus safer.

Be the first to earn a spot here.

Submit a report
Report

Submit a vulnerability

Choose the channel that works best for you. Include clear reproduction steps and the expected vs. actual behavior.

FAQ

Frequently asked questions

Who is eligible to participate?
Anyone can participate as long as they follow the rules of engagement. You do not need to be an existing Octopus user. Employees and contractors of Octopus are not eligible.
What happens if someone else reports the same vulnerability?
We reward the first valid report. If you submit a duplicate, we will let you know and credit will go to the original reporter.
How quickly will I hear back?
We aim to acknowledge your report within 3 business days and provide an initial assessment within 10 business days.
Can I disclose publicly after the fix?
Yes. Once we confirm the vulnerability is fixed, you are free to publish a write-up. We encourage responsible disclosure and will credit you in our release notes.
What if a vulnerability spans multiple severity levels?
We assess based on the maximum realistic impact. If you demonstrate a chain that escalates impact, we reward the highest severity in the chain.
Am I legally protected?
Yes. As long as you follow the rules of engagement, we will not pursue legal action. We consider security research conducted under this program as authorized.

Octopus reserves the right to modify or cancel this program at any time.
Reward amounts are at our discretion based on impact and quality of the report.