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 |
| Able to view hackerone reports attachmentsAnalysed#979787 | Valid | Information Disclosure | Critical | 2022-07-11 | – | 103 |
| Access to GitLab's Slack by abusing issue creation from e-mailAnalysed#218230 | Valid | Authentication | Critical | 2017-09-21 | – | 54 |
| all private tokens are leaked to an unauthenticated attackerAnalysed#268794 | Valid | Access Control | Critical | 2017-09-21 | – | 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.