Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| 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 |
| 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 |
| Stored XSS in repository file viewerAnalysed#1072868 | Valid | Cross-site Scripting | Medium | 2022-05-19 | $2,000 | 29 |
| 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 |
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,935 analysed so far), which can be wrong. Data as of 2026-11-15.