Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Shared-channel BETA persists integration after unshare#291822 | Valid | Input Validation and Logic | Medium | 2018-04-25 | $750 | 13 |
| URL filter bypass in Enterprise GridAnalysed#500348 | Valid | Input Validation and Logic | Low | 2020-02-14 | $100 | 32 |
| CSS Injection to disable app & potential message exfilAnalysed#679969 | Valid | Input Validation and Logic | Medium | 2019-11-09 | – | 37 |
| Bypass invite accept for victimAnalysed#1663361 | Valid | Input Validation and Logic | Medium | 2023-02-17 | – | 84 |
| URL link spoofingAnalysed#481472 | Valid | Input Validation and Logic | Low | 2020-04-26 | $250 | 362 |
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,437 analysed so far), which can be wrong. Data as of 2026-11-15.