Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Read files on application server, leads to RCEAnalysed#178152 | Valid | Information Disclosure | Critical | 2016-11-03 | – | 114 |
| Boards leak private label names and desciptions#162147 | Valid | Information Disclosure | – | 2016-09-02 | – | 10 |
| Attacker can extract list of private project's project members#128051 | Valid | Information Disclosure | – | 2016-08-01 | – | 10 |
| Private snippets in public / internal projects leaked though GitLab API#134305 | Valid | Information Disclosure | – | 2016-05-03 | – | 7 |
| Labels created in private projects are leaked#132777 | Valid | Information Disclosure | – | 2016-05-03 | – | 7 |
| Confidential issues leaked in public projects when attached to milestone#134300 | Valid | Information Disclosure | – | 2016-05-03 | – | 5 |
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, where there is one, which can be wrong. Data as of 2026-11-15.