Skip to content

Bug bounty reports15,219

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

Program:GitLab
Status
Severity:Medium
Clear
Weakness
Year
Bounty paid2
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 filters4 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
ReDoS due to device-detector parsing user agents#1772063ValidDenial of ServiceMedium2024-10-08–23
Maintainer can leak sentry token by changing the configured URL (fix bypass)#2104591ValidInformation DisclosureMedium2024-10-08–32
DOS: taking down a 1k users Gitlab EE instance or multiple Sidekiq instances by importing a malicious repo from a Github EE self-hosted server#2499070ValidDenial of ServiceMedium2024-10-09$2,30064
IDOR Exposes All Machine Learning Models#2528293ValidInsecure Direct Object ReferenceMedium2024-10-01$1,160117

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

Updated AboutDevelopersSign in