Skip to content

Bug bounty reports15,219

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

Program:GitHub
Status
Severity
Weakness
Year:2026
Clear
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters9 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Add labels to arbitrary issues/prs via Memex Bulk Update to compromise github actions label gating#3527788ValidInsecure Direct Object ReferenceMedium2026-08-25–46
PATs without the required scope can leak issues#3522254ValidAccess ControlMedium2026-03-19–59
GitHub user to server tokens can create issues in any public repository#3641229ValidAccess ControlMedium2026-07-22–62
Add labels to arbitrary issues/prs & compromise github actions label checks#3527771ValidInsecure Direct Object ReferenceMedium2026-03-19–71
OAuth redirect uri validation bypass for :proxima_first_party_sync apps#3588801ValidOpen RedirectHigh2026-07-21–79
GitHub scoped user to server tokens can escape their installation#3638909ValidAccess ControlHigh2026-07-29–80
Missing Access Control in MigrationFile allows attacker to upload files to any Migration#3506183ValidInsecure Direct Object ReferenceHigh2026-03-05–92
Able to bypass authorization logic and gain more access then intended#3713965ValidNo weakness recordedMedium2026-07-15–105
Cross-repository IDOR in `/settings/security_analysis/bypass_reviewers` allows unauthorized delegated bypass reviewer modification#3560256ValidInsecure Direct Object ReferenceMedium2026-05-19–108

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 (348 analysed so far), which can be wrong. Data as of 2026-11-14.

Updated AboutDevelopersSign in