Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Potential denial of service in hackerone.com/teams/new#13748 | Valid | Denial of Service | – | 2014-06-20 | – | 3 |
| Pending member invitations are not revoked on program name change#275293 | Informative | Information Disclosure | None | 2017-11-18 | – | 2 |
| Denial of service in report view.#140720 | Informative | Denial of Service | – | 2016-05-27 | – | 2 |
| User with Read-Only permissions can edit the SwagAwarded Activities on Bug Reports#118731 | Valid | Access Control | – | 2016-04-01 | – | 2 |
| User with Read-Only permissions can manually public disclosure the report#118718 | Valid | Misconfiguration and Insecure Design | – | 2016-04-21 | $500 | 2 |
| Requesting unknown file type returns Ruby object w/ address#109420 | Valid | Information Disclosure | – | 2016-02-19 | – | 2 |
| Notification of previous signed out user leakage.#26395 | Informative | Information Disclosure | – | 2014-09-01 | – | 2 |
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,437 analysed so far), which can be wrong. Data as of 2026-11-15.