Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Missing memory corruption protection on Windows release built#380102 | Valid | Memory Corruption | Medium | 2020-08-14 | – | 2 |
| nextcloud.com: Mail Bombing ( No Rate Limiting On Sending Emails On Contact us Page)#145458 | Valid | Memory Corruption | – | 2016-07-17 | – | 4 |
| High memory usage for generating preview of broken image#1261225 | Valid | Memory Corruption | Low | 2022-03-09 | – | 10 |
| Persistent SMTP header injection via identity `organization` / `name`#3913012 | Valid | Memory Corruption | None | 2026-09-18 | – | 19 |
| Improper Input Validation and Integer Overflow in timeamount parameter of files_retention app#3521639 | Valid | Memory Corruption | Low | 2026-09-05 | – | 23 |
| SMTP header injection via C-escape `\r` in the recipient display name#3913007 | Valid | Memory Corruption | None | 2026-10-18 | – | 23 |
| 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 |
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,699 analysed so far), which can be wrong. Data as of 2026-11-15.