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
Bounty paid2
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique:Missing authorisation check
Clear filters3 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Arbitrary Read of Another Users private repository without AuthorizationAnalysed#3124517ValidInsecure Direct Object ReferenceHigh2025-09-23$10,000276
Github Apps can use Scoped-User-To-Server Tokens to Obtain Full Access to User's Projects in Project V2 GraphQL apiAnalysed#1711938ValidAccess Control–2023-01-26–198
Authentication bypass on gist.github.com through SSH CertificatesAnalysed#1901040ValidAccess ControlHigh2023-04-20$10,000182

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

Updated AboutDevelopersSign in