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 |
| HTML Injection inside Slack promotional emails#321029 | Valid | No weakness recorded | Low | 2018-07-30 | $100 | 13 |
| HTTP parameter pollution from outdated Greenhouse.io JS dependencyAnalysed#335339 | Valid | Injection and Smuggling | Medium | 2018-07-19 | – | 26 |
| The POODLE attack (SSLv3 supported) at status.slack.comAnalysed#375097 | Valid | Cryptography | Medium | 2018-11-28 | – | 44 |
| Internal SSRF bypass using slash commands at api.slack.comAnalysed#356765 | Valid | Server-Side Request Forgery | Medium | 2018-07-12 | – | 51 |
| Unauthenticated LFI revealing log informationAnalysed#272578 | Valid | Information Disclosure | High | 2018-01-26 | – | 123 |
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.