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 |
| Authentication bypass on gist.github.com through SSH CertificatesAnalysed#1901040 | Valid | Access Control | – | 2023-04-20 | $10,000 | 182 |
| CSRF protection bypass in GitHub Enterprise management console#1497169 | Valid | Cross-Site Request Forgery | – | 2022-04-13 | $10,000 | 152 |
| Information Leakage via Clicked Link in GitHub Repository (Fingerprinting)#2505761 | Valid | Information Disclosure | Medium | 2024-10-17 | $4,000 | 72 |
| DoS via markdown API from unauthenticated user#1619604 | Valid | Denial of Service | – | 2022-12-13 | $4,000 | 54 |
| Delimiter injection in GitHub Actions core.exportVariable#1625652 | Valid | Misconfiguration and Insecure Design | – | 2022-08-18 | $4,617 | 39 |
| Command injection in GitHub Actions ContainerStepHost#1637621 | Valid | Injection and Smuggling | – | 2022-11-03 | $4,000 | 32 |
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.