Skip to content

Bug bounty reports15,219

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

Program:GitLab
Status
Severity:Low
Clear
Weakness
Year
Bounty paid3
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed:No account
Technique
Clear filters7 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Snippet JS template allows attacker to read a user's private snippetsAnalysed#348443ValidInformation DisclosureLow2019-03-03$300165
Remove obsolete domain from handbook subdomainAnalysed#2599840ValidMisconfiguration and Insecure DesignLow2024-10-01–72
Access Projects And create projects in gitlab pre production serverAnalysed#540711ValidAccess ControlLow2019-08-28–28
No redirect_uri in the db for web-internal clientKey leads to one-click DoS on gitter.imAnalysed#702987ValidDenial of ServiceLow2020-05-15–26
A profile page of a user can be denied from loading by appending .html to the usernameAnalysed#475098ValidMisconfiguration and Insecure DesignLow2021-08-30$20026
Claiming package names in GitLab's automatic package referencer.Analysed#462503ValidInput Validation and LogicLow2019-04-05$1,00026
Last build status and coverage leaked to unauthorized usersAnalysed#477222ValidInformation DisclosureLow2019-09-01–24

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.