Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Access body and title of Internal Repo Issues in ProjectsAnalysed#2501036 | Valid | Information Disclosure | Medium | 2024-07-31 | – | 100 |
| Information Leakage via Clicked Link in GitHub Repository (Fingerprinting)Analysed#2505761 | Valid | Information Disclosure | Medium | 2024-10-17 | $4,000 | 72 |
| View private repository NWO of deploy key via internal LFS APIAnalysed#2469713 | Valid | Access Control | Medium | 2024-07-23 | – | 70 |
| View Repo and Title of Any Private Check RunAnalysed#2210179 | Valid | Insecure Direct Object Reference | Medium | 2024-01-08 | – | 64 |
| Source Code and data exfiltration via Github CopilotAnalysed#2383092 | Valid | Command and Code Injection | Low | 2024-08-19 | – | 63 |
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 (1,683 analysed so far), which can be wrong. Data as of 2026-11-15.