Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| TURN server allows TCP and UDP proxying to internal network, localhost and meta-data servicesAnalysed#333419 | Valid | Server-Side Request Forgery | Critical | 2020-03-12 | $3,500 | 323 |
| Tricking the "Create snippet" feature into displaying the wrong filetype can lead to RCE on Slack usersAnalysed#833080 | Valid | File and Path Handling | High | 2020-06-30 | $1,500 | 101 |
| Many Slack teams can be joined by abusing an improperly configured support@ inboxAnalysed#239623 | Valid | Authentication | – | 2017-10-21 | – | 88 |
| Access to some Slack workspace metadata and settings available to unauthorized partiesAnalysed#130133 | Valid | Authentication | – | 2020-11-10 | $7,000 | 60 |
| Internal SSRF bypass using slash commands at api.slack.comAnalysed#356765 | Valid | Server-Side Request Forgery | Medium | 2018-07-12 | – | 51 |
| Store XSSAnalysed#187410 | Valid | Cross-site Scripting | High | 2017-01-01 | – | 44 |
| Snooping into messages via email serviceAnalysed#163938 | Valid | Authentication | – | 2016-09-14 | – | 30 |
| DoS on the Direct MessagesAnalysed#746003 | Valid | Denial of Service | Medium | 2020-11-11 | $500 | 29 |
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.