Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| SSRF via git Repo by URL Abuse#191216 | Duplicate | Server-Side Request Forgery | – | 2017-11-28 | – | 3 |
| Potensial SSRF via Git repository URL#359288 | Duplicate | Server-Side Request Forgery | – | 2018-07-16 | – | 7 |
| GraphQL Query leads to sensitive information disclosure#985124 | Duplicate | Information Disclosure | – | 2021-03-08 | – | 12 |
| Inadequate cache control in gitter allows to view private chat room#493791 | Duplicate | Authentication | – | 2019-03-08 | – | 13 |
| Blind SSRF in FogBugz project import#709951 | Duplicate | Server-Side Request Forgery | – | 2023-05-30 | – | 14 |
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 (227 analysed so far), which can be wrong. Data as of 2026-11-14.