Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Confidential data of users and limited metadata of programs and reports accessible via GraphQLAnalysed#489146 | Valid | Information Disclosure | Critical | 2019-02-03 | – | 1,033 |
| How the Bug stole hackingAnalysed#762510 | Valid | Insecure Direct Object Reference | None | 2019-12-20 | – | 471 |
| Team object in GraphQL disclosed of private programs via the industryAnalysed#707406 | Valid | No weakness recorded | Low | 2019-11-23 | $500 | 72 |
| Disclosing a private program in an external link if program is pausedAnalysed#418474 | Valid | No weakness recorded | Low | 2019-06-28 | $500 | 44 |
| A small set of users were assigned someone else's payout preferenceAnalysed#498845 | Valid | Information Disclosure | Low | 2019-02-20 | – | 30 |
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, where there is one, which can be wrong. Data as of 2026-11-15.