Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| How the Bug stole hackingAnalysed#762510 | Valid | Insecure Direct Object Reference | None | 2019-12-20 | – | 471 |
| How the Arch Angel stole Live EventsAnalysed#2285198 | Valid | No weakness recorded | None | 2023-12-15 | – | 98 |
| Blind Stored XSS in HackerOne's Sal 4.1.4.2149 (sal.████.com)Analysed#995995 | Valid | Cross-site Scripting | None | 2020-11-09 | – | 84 |
| Team object in GraphQL that have a published external program may expose existence of a private programAnalysed#347937 | Valid | Information Disclosure | None | 2018-07-04 | – | 39 |
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,365 analysed so far), which can be wrong. Data as of 2026-11-15.