Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Cross-repository IDOR in `/settings/security_analysis/bypass_reviewers` allows unauthorized delegated bypass reviewer modificationAnalysed#3560256 | Valid | Insecure Direct Object Reference | Medium | 2026-05-19 | – | 108 |
| Able to bypass authorization logic and gain more access then intendedAnalysed#3713965 | Valid | No weakness recorded | Medium | 2026-07-15 | – | 105 |
| Add labels to arbitrary issues/prs & compromise github actions label checksAnalysed#3527771 | Valid | Insecure Direct Object Reference | Medium | 2026-03-19 | – | 71 |
| GitHub user to server tokens can create issues in any public repository#3641229 | Valid | Access Control | Medium | 2026-07-22 | – | 62 |
| PATs without the required scope can leak issuesAnalysed#3522254 | Valid | Access Control | Medium | 2026-03-19 | – | 59 |
| Add labels to arbitrary issues/prs via Memex Bulk Update to compromise github actions label gatingAnalysed#3527788 | Valid | Insecure Direct Object Reference | Medium | 2026-08-25 | – | 46 |
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.