Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Ability To Delete User(s) Account Without User InteractionAnalysed#928255 | Valid | Misconfiguration and Insecure Design | High | 2021-03-17 | – | 221 |
| CSRF on /api/graphql allows executing mutations through GET requestsAnalysed#1122408 | Valid | Cross-Site Request Forgery | High | 2021-08-02 | $3,370 | 88 |
| Cache poisoning Denial of Service affecting assets.gitlab-static.netAnalysed#1160407 | Valid | Denial of Service | High | 2021-12-22 | – | 83 |
| Remote hacker can download all the files of master branch in public projects where everything is members only.Analysed#1043480 | Valid | Authentication | Medium | 2021-02-15 | – | 31 |
| Drive-by arbitrary file deletion in the GDK via letter_opener_web gemAnalysed#1353103 | Valid | Cross-Site Request Forgery | Medium | 2021-11-12 | $750 | 27 |
| A profile page of a user can be denied from loading by appending .html to the usernameAnalysed#475098 | Valid | Misconfiguration and Insecure Design | Low | 2021-08-30 | $200 | 26 |
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 (4,614 analysed so far), which can be wrong. Data as of 2026-11-15.