Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| IDOR Exposes All Machine Learning ModelsAnalysed#2528293 | Valid | Insecure Direct Object Reference | Medium | 2024-10-01 | $1,160 | 117 |
| Subdomain takeover in Gitlab pagesAnalysed#2523654 | Valid | Misconfiguration and Insecure Design | Low | 2024-10-09 | – | 79 |
| Stored-XSS injected in Wiki page via Banzai pipelineAnalysed#2257080 | Valid | Cross-site Scripting | High | 2024-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#2499070 | Valid | Denial of Service | Medium | 2024-10-09 | $2,300 | 64 |
| HTML injection possible with soft email confirmations when Administrator manually confirms attacker email addressAnalysed#1935628 | Valid | Injection and Smuggling | Low | 2024-10-08 | $1,060 | 61 |
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 (4,182 analysed so far), which can be wrong. Data as of 2026-11-15.