Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Internal IP addresses range and AWS cluster region leaked in a Github repository#877303 | Informative | Information Disclosure | None | 2020-07-24 | – | – |
| Hard coded Username and password in GiHub commit#877402 | Informative | Authentication | None | 2020-07-24 | – | – |
| Configuartion [Sensitive] Information Disclosure#774872 | Informative | Information Disclosure | None | 2020-10-22 | – | 1 |
| There is any issue No valid SPF Records#864696 | Duplicate | Authentication | None | 2020-07-24 | – | 1 |
| Private IP addresses Disclosure#908880 | Informative | Information Disclosure | None | 2020-07-23 | – | 1 |
| Fake email from <any_name>@kubernetes.io to any other email#918243 | Duplicate | No weakness recorded | None | 2020-07-24 | – | 3 |
| Clickjacking#832593 | Informative | Misconfiguration and Insecure Design | None | 2020-07-23 | – | 5 |
| Index Out Of Bounds in protobuf unmarshallingAnalysed#1073363 | Valid | Memory Corruption | None | 2021-08-30 | $250 | 13 |
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.