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 | – | 2019-02-03 | – | 1,033 |
| How the Bug stole hackingAnalysed#762510 | Valid | Insecure Direct Object Reference | – | 2019-12-20 | – | 471 |
| Insecure Direct Object Reference (IDOR) Allows Viewing Private Report Details via /bugs.json EndpointAnalysed#2487889 | Valid | Insecure Direct Object Reference | Critical | 2024-05-23 | – | 266 |
| Markdown parsing issue enables insertion of malicious tags and event handlersAnalysed#299728 | Valid | Cross-site Scripting | – | 2018-01-29 | $5,000 | 184 |
| Bypassing HackerOne 2FA due to race conditionAnalysed#2598548 | Valid | Input Validation and Logic | Medium | 2024-10-30 | – | 139 |
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 (549 analysed so far), which can be wrong. Data as of 2026-11-14.