Program Overview
GitLab runs a bug bounty program on HackerOne. The program has 20 in-scope assets and is managed by HackerOne's triage team.
20
In-Scope Assets
6h
Avg Response
92%
Efficiency
41d
Avg Bounty Time
61d
Avg Resolve
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| *.gitlab.net | WILDCARD | Medium | Bounty |
| *.gitlab.org | WILDCARD | Medium | Bounty |
| *.gitlap.com | WILDCARD | Medium | Bounty |
| GitLab for Jira Cloud | OTHER | Medium | Bounty |
| Other non-production infrastructure | OTHER | Medium | Bounty |
| Your Own GitLab Instance | OTHER | Critical | Bounty |
| about.gitlab.com | URL | Medium | Bounty |
| advisories.gitlab.com | URL | Medium | Bounty |
| customers.gitlab.com | URL | Critical | Bounty |
| design.gitlab.com | URL | Medium | Bounty |
| docs.gitlab.com | URL | Medium | Bounty |
| gitlab.com | URL | Critical | Bounty |
| https://gitlab.com/gitlab-org/gitaly | SOURCE_CODE | Critical | Bounty |
| https://gitlab.com/gitlab-org/gitlab | SOURCE_CODE | Critical | Bounty |
| https://gitlab.com/gitlab-org/gitlab-pages | SOURCE_CODE | Critical | Bounty |
| https://gitlab.com/gitlab-org/gitlab-runner | SOURCE_CODE | Critical | Bounty |
| https://gitlab.com/gitlab-org/gitlab-shell | SOURCE_CODE | Critical | Bounty |
| https://gitlab.com/gitlab-org/gitlab-vscode-extension | SOURCE_CODE | Critical | Bounty |
| https://gitlab.com/gitlab-org/opstrace/opstrace | SOURCE_CODE | Critical | Bounty |
| registry.gitlab.com | URL | Critical | Bounty |
Out-of-Scope Assets
- *.gitlab-private.org
- *.gitlab.cn
- *.runway.gitlab.net
- *.service-now.com
- alerts.gitlab.com
- aptly.gitlab.com
- dashboards.gitlab.com
- federal-support.gitlab.com
- forum.gitlab.com
- gitlab.biterg.io
- gitlabdemo.cloud
- gitlabsandbox.net
- gitlabtraining.cloud
- https://gitlab.com/gitlab-org/cli/
- https://gitlab.com/gitlab-org/opstrace/opstrace-ui
- ir.gitlab.com
- levelup.gitlab.com
- packages.gitlab.com
- partners.gitlab.com
- shop.gitlab.com
Tips for Hacking GitLab
- Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
- Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
- Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
- Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
- Write clear reports — Include steps to reproduce, impact assessment, and suggested remediation. Use Burp Suite to capture evidence.
Frequently Asked Questions
How do I start hacking GitLab?
Sign up on HackerOne, read the program policy carefully, review the in-scope assets listed above, and start testing. Always stay within scope and follow responsible disclosure guidelines.
Does GitLab pay bounties?
Yes, GitLab offers monetary rewards for valid security vulnerabilities.
What types of vulnerabilities does GitLab accept?
GitLab accepts reports for vulnerabilities found in their 20 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.