Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:GitHub
Status
Severity
Weakness:Access Control
Clear
Year:2026
Clear
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account2
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters3 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
GitHub scoped user to server tokens can escape their installationAnalysed#3638909ValidAccess ControlHigh2026-07-29–80
GitHub user to server tokens can create issues in any public repository#3641229ValidAccess ControlMedium2026-07-22–62
PATs without the required scope can leak issuesAnalysed#3522254ValidAccess ControlMedium2026-03-19–59

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, where there is one, which can be wrong. Data as of 2026-11-15.