Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Account Takeover via Password Reset without user interactionsAnalysed#2293343 | Valid | Access Control | Critical | 2025-02-26 | $35,000 | 989 |
| Full access to internal Gitlab instances at redash.gitlab.com, dashboards.gitlab.com, prometheus.gitlab.comAnalysed#498964 | Valid | Access Control | Critical | 2019-04-19 | – | 306 |
| Group search leaks private MRs, code, commitsAnalysed#692252 | Valid | Access Control | High | 2019-12-14 | – | 212 |
| GraphQL query "namespace" leaks dataAnalysed#614355 | Valid | Access Control | Medium | 2019-12-03 | – | 64 |
| Bypassing push rules via MRs created by EmailAnalysed#526570 | Valid | Access Control | Medium | 2019-10-01 | – | 36 |
| Mailgun misconfiguration leads to email snooping and postmaster@-access on email.mg.gitlab.comAnalysed#174983 | Valid | Access Control | – | 2016-12-06 | – | 31 |
| Access Projects And create projects in gitlab pre production serverAnalysed#540711 | Valid | Access Control | Low | 2019-08-28 | – | 28 |
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,437 analysed so far), which can be wrong. Data as of 2026-11-15.