Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Arbitrary Read of Another Users private repository without AuthorizationAnalysed#3124517 | Valid | Insecure Direct Object Reference | High | 2025-09-23 | $10,000 | 276 |
| Cross-repository IDOR in `/settings/security_analysis/bypass_reviewers` allows unauthorized delegated bypass reviewer modification#3560256 | Valid | Insecure Direct Object Reference | Medium | 2026-05-19 | – | 108 |
| Missing Access Control in MigrationFile allows attacker to upload files to any Migration#3506183 | Valid | Insecure Direct Object Reference | High | 2026-03-05 | – | 92 |
| Add labels to arbitrary issues/prs & compromise github actions label checks#3527771 | Valid | Insecure Direct Object Reference | Medium | 2026-03-19 | – | 71 |
| View Repo and Title of Any Private Check Run#2210179 | Valid | Insecure Direct Object Reference | – | 2024-01-08 | – | 64 |
| Add labels to arbitrary issues/prs via Memex Bulk Update to compromise github actions label gating#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 (348 analysed so far), which can be wrong. Data as of 2026-11-14.