Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Ability to bypass email verification for OAuth grants results in accounts takeovers on 3rd partiesAnalysed#922456 | Valid | Authentication | High | 2020-10-01 | $3,000 | 257 |
| Bypass Email Verification -- Able to Access Internal Gitlab Services that use Login with Gitlab and Perform Check on email domainAnalysed#565883 | Valid | Input Validation and Logic | Medium | 2019-08-30 | – | 249 |
| Bypass Email Verification using Salesforce -- Reproducible in gitlab.comAnalysed#617896 | Valid | Misconfiguration and Insecure Design | High | 2019-12-13 | – | 55 |
| Access to GitLab's Slack by abusing issue creation from e-mailAnalysed#218230 | Valid | Authentication | Critical | 2017-09-21 | – | 54 |
Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (3,686 analysed so far), which can be wrong. Data as of 2026-11-15.