Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| SSRF on project import via the remote_attachment_url on a NoteAnalysed#826361 | Valid | Server-Side Request Forgery | High | 2020-06-07 | $10,000 | 359 |
| Server Side Request Forgery mitigation bypassAnalysed#632101 | Valid | Server-Side Request Forgery | High | 2020-04-18 | – | 350 |
| GitLab::UrlBlocker validation bypass leading to full Server Side Request ForgeryAnalysed#541169 | Valid | Server-Side Request Forgery | High | 2019-12-12 | – | 72 |
| SSRF in CI after first runAnalysed#369451 | Valid | Server-Side Request Forgery | Medium | 2019-04-12 | – | 72 |
| FogBugz import attachment full SSRF requiring vulnerability in *.fogbugz.comAnalysed#1092230 | Valid | Server-Side Request Forgery | High | 2021-07-13 | – | 58 |
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 (2,699 analysed so far), which can be wrong. Data as of 2026-11-15.