Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Privilege Escalation to Root SSH Access via Pre-Receive Hook Environment in GitHub Enterprise ServerAnalysed#2336236 | Valid | No weakness recorded | High | 2024-09-13 | – | 71 |
| RC Between GitHub's Repo Transfer REST API and updateTeamsRepository GraphQL Mutation Results in Covert and Persistent Admin Access RetentionAnalysed#2216036 | Valid | Misconfiguration and Insecure Design | Medium | 2024-01-12 | – | 50 |
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.