Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Able to bypass authorization logic and gain more access then intendedAnalysed#3713965 | Valid | No weakness recorded | Medium | 2026-07-15 | – | 105 |
| Invite tokens have Insufficient entropy in GHES Management ConsoleAnalysed#2197801 | Valid | Cryptography | Medium | 2024-01-12 | – | 81 |
| Self XSS in Tag name pattern field /<username>/<reponame>/settings/tag_protection/newAnalysed#2246576 | Valid | Cross-site Scripting | Medium | 2024-04-15 | – | 76 |
| View Repo and Title of Any Private Check RunAnalysed#2210179 | Valid | Insecure Direct Object Reference | Medium | 2024-01-08 | – | 64 |
| Delimiter injection in GitHub Actions core.exportVariableAnalysed#1625652 | Valid | Misconfiguration and Insecure Design | Medium | 2022-08-18 | $4,617 | 39 |
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 (3,935 analysed so far), which can be wrong. Data as of 2026-11-15.