Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| SMTP header injection via C-escape `\r` in the recipient display nameAnalysed#3913007 | Valid | Memory Corruption | None | 2026-10-18 | – | 23 |
| Self XSS when sending HTML as a comment in the Deck appAnalysed#2058556 | Valid | Cross-site Scripting | None | 2024-01-18 | – | 20 |
| Persistent SMTP header injection via identity `organization` / `name`Analysed#3913012 | Valid | Memory Corruption | None | 2026-09-18 | – | 19 |
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.