Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Github Apps can use Scoped-User-To-Server Tokens to Obtain Full Access to User's Projects in Project V2 GraphQL apiAnalysed#1711938 | Valid | Access Control | High | 2023-01-26 | – | 198 |
| Rogue collaborators and ambiguous branch names in GitHubAnalysed#1831528 | Valid | Input Validation and Logic | – | 2023-12-05 | – | 43 |
| Smuggling content in PR with refs/replace in GitHubAnalysed#1938106 | Valid | Injection and Smuggling | Medium | 2023-08-01 | – | 35 |
| Git Reference Ambiguity in GitHub - Commit Smuggling, Account Takeover, and Remote Code ExecutionAnalysed#2017600 | Valid | Injection and Smuggling | Medium | 2023-11-29 | – | 25 |
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 (4,182 analysed so far), which can be wrong. Data as of 2026-11-15.