Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Race condition in GitLab import, giving access to other people their imports due to filename collisionAnalysed#214028 | Valid | Information Disclosure | Low | 2017-10-03 | – | 22 |
| [Markdown] Stored XSS via character encoding parser bypassAnalysed#270999 | Valid | Cross-site Scripting | Medium | 2017-10-18 | – | 20 |
| CSV injection in gitlab.com via issues export feature.Analysed#216243 | Valid | Command and Code Injection | Medium | 2017-07-21 | – | 20 |
| SSRF vulnerability in gitlab.com via project import.Analysed#215105 | Valid | Server-Side Request Forgery | Medium | 2017-11-09 | – | 20 |
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.