Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| June 2022 Incident ReportAnalysed#1622449 | Valid | No weakness recorded | Critical | 2022-07-01 | – | 426 |
| Account takeover of existing HackerOne accounts through SCIM provisioningAnalysed#3178999 | Valid | Access Control | High | 2025-07-17 | – | 232 |
| Program admins could add verified domains to an organizationAnalysed#2323303 | Valid | Access Control | Low | 2024-03-07 | – | 83 |
| Near to Infinite loop when changing Group's name that has API token as Team MemberAnalysed#880187 | Valid | No weakness recorded | Medium | 2020-07-23 | $2,500 | 77 |
| Disclosure of Email title report in quick award paypout email (no content mode)Analysed#689997 | Valid | Information Disclosure | Low | 2019-10-11 | $500 | 62 |
| IE 11 Self-XSS on Jira Integration Preview Base LinkAnalysed#212721 | Valid | Cross-site Scripting | Low | 2017-03-29 | $750 | 42 |
| User with privilege to maintain External Programs can update certain churned HackerOne programsAnalysed#411930 | Valid | Access Control | Low | 2018-10-25 | $500 | 41 |
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.