Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| CSRF protection bypass in GitHub Enterprise management consoleAnalysed#1497169 | Valid | Cross-Site Request Forgery | – | 2022-04-13 | $10,000 | 152 |
| Managing Pages#1690427 | Valid | Access Control | – | 2022-12-22 | – | 54 |
| 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 |
| [Git Gud] GitHub.com Svnbridge memcached deserialization vulnerability chain leading to Remote Code Execution#1593913 | Valid | Deserialization and Object Injection | – | 2022-11-16 | – | 14 |
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 (549 analysed so far), which can be wrong. Data as of 2026-11-14.