Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Lack of validation before assigning custom domain names leading to abuse of GitLab pages service#296907 | Informative | Input Validation and Logic | – | 2018-02-01 | – | 2 |
| Possibilty to purchase Ultimate - 1 Year (EDU or OSS)#882848 | Valid | Input Validation and Logic | – | 2020-11-02 | – | 23 |
| Claiming package names in GitLab's automatic package referencer.#462503 | Valid | Input Validation and Logic | – | 2019-04-05 | $1,000 | 26 |
| Using GitLab to monitor and hijack domains in mass quantity.#312118 | Valid | Input Validation and Logic | – | 2018-02-21 | $750 | 39 |
| 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 | – | 2019-08-30 | – | 249 |
| An attacker can run pipeline jobs as arbitrary userAnalysed#894569 | Valid | Input Validation and Logic | – | 2020-08-26 | $12,000 | 307 |
| Bypass of GitLab CI runner slash fix in YAML validationAnalysed#409395 | Valid | Input Validation and Logic | – | 2019-04-10 | – | 363 |
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 (227 analysed so far), which can be wrong. Data as of 2026-11-14.