Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| No rate limiting for confirmation email lead to huge Mass mailingsAnalysed#997070 | Valid | Input Validation and Logic | Medium | 2020-11-04 | – | 82 |
| Improper input validation On Exported deep-link handler crashes `FileDisplayActivity` on crafted external URL — Denial-of-ServiceAnalysed#3399016 | Valid | Memory Corruption | None | 2026-05-01 | – | 65 |
| Improper input validation in emoji field leads to sidebar UI denial of serviceAnalysed#3599470 | Valid | Input Validation and Logic | Low | 2026-09-20 | – | 64 |
| Inviting excessive long email addresses to a calendar event makes the server unresponsiveAnalysed#2058337 | Valid | Denial of Service | Medium | 2023-10-16 | – | 46 |
| End-to-end encrypted file-drops can be made inaccessibleAnalysed#1914115 | Valid | Access Control | High | 2023-06-22 | $400 | 43 |
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 (2,444 analysed so far), which can be wrong. Data as of 2026-11-15.