Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| DOS via Mutation Aliasing in GraphQL Account Recovery Phone Number Verification APIAnalysed#3287208 | Valid | No weakness recorded | – | 2026-04-16 | – | 185 |
| Scope information is leaked when visiting policy scopes tab of any External ProgramAnalysed#1868473 | Valid | Access Control | Medium | 2023-03-10 | – | 86 |
| Ability to bulk submit reports via query named based batchingAnalysed#2166697 | Valid | Misconfiguration and Insecure Design | Low | 2024-06-19 | $500 | 37 |
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,686 analysed so far), which can be wrong. Data as of 2026-11-15.