Skip to content

Bug bounty reports15,219

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

Program:GitLab
Status:Valid
Clear
Severity
Weakness
Year:2024
Clear
Bounty paid3
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
IDOR Exposes All Machine Learning ModelsAnalysed#2528293ValidInsecure Direct Object ReferenceMedium2024-10-01$1,160117
Subdomain takeover in Gitlab pagesAnalysed#2523654ValidMisconfiguration and Insecure DesignLow2024-10-09–79
Remove obsolete domain from handbook subdomainAnalysed#2599840ValidMisconfiguration and Insecure DesignLow2024-10-01–72
Stored-XSS injected in Wiki page via Banzai pipelineAnalysed#2257080ValidCross-site ScriptingHigh2024-05-28–71
DOS: taking down a 1k users Gitlab EE instance or multiple Sidekiq instances by importing a malicious repo from a Github EE self-hosted serverAnalysed#2499070ValidDenial of ServiceMedium2024-10-09$2,30064
HTML injection possible with soft email confirmations when Administrator manually confirms attacker email addressAnalysed#1935628ValidInjection and SmugglingLow2024-10-08$1,06061
Maintainer can leak sentry token by changing the configured URL (fix bypass)Analysed#2104591ValidInformation DisclosureMedium2024-10-08–32
ReDoS due to device-detector parsing user agentsAnalysed#1772063ValidDenial of ServiceMedium2024-10-08–23

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.