Skip to content

Bug bounty reports15,219

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

Program:GitHub
Status:Valid
Clear
Severity
Weakness
Year
Bounty paid2
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed:No account
Technique
Clear filters3 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
SAML Signature verification bypass allows logging into any user (with specific conditions)Analysed#2579939ValidAccess ControlCritical2024-10-10–196
Authentication bypass on gist.github.com through SSH CertificatesAnalysed#1901040ValidAccess ControlHigh2023-04-20$10,000182
CSRF protection bypass in GitHub Enterprise management consoleAnalysed#1497169ValidCross-Site Request Forgery–2022-04-13$10,000152

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