Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Reputation gain split by company can be used to track the existence of otherwise undisclosed reports#311449 | N/A | Information Disclosure | Low | 2018-02-02 | – | 4 |
| Spamming any user from Reset Password Function#12782 | N/A | Misconfiguration and Insecure Design | – | 2016-05-03 | – | 5 |
| Reputation Manipulation (Theoretical)#132057 | N/A | Misconfiguration and Insecure Design | – | 2016-04-19 | – | 9 |
| Report title and issue information prepopulated#111868 | N/A | No weakness recorded | – | 2016-07-15 | – | 15 |
| Ability to monitor reports' submission in real time#159890 | N/A | Access Control | – | 2016-08-17 | – | 16 |
| Session hijacking attack#163381 | N/A | No weakness recorded | – | 2019-12-06 | – | 21 |
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 (3,187 analysed so far), which can be wrong. Data as of 2026-11-15.