Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Adding everyone to the repo due to the lack of rate limit#978768 | N/A | Insecure Direct Object Reference | – | 2020-09-14 | – | 8 |
| Double linking cause XSS (but blokeced by CSP in gitlab.com)#729341 | N/A | Cross-site Scripting | – | 2020-01-20 | – | 6 |
| Guests Will Disclose the Private Project Full Activity Via Project Activity Feeds#491319 | N/A | Information Disclosure | – | 2019-02-08 | – | 5 |
| Email notification about login email changed is not received when using verified linked email address#801973 | N/A | Misconfiguration and Insecure Design | – | 2020-03-25 | – | 3 |
| No Restriction on password#1696814 | N/A | No weakness recorded | – | 2022-09-13 | – | 2 |
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 (348 analysed so far), which can be wrong. Data as of 2026-11-14.