Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| DoS on the Issue page by exploiting Mermaid.Analysed#470067 | Valid | Denial of Service | Medium | 2019-05-13 | $3,000 | 145 |
| DoS attack via comment on IssueAnalysed#557154 | Valid | Denial of Service | Low | 2019-11-21 | $1,000 | 84 |
| 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 |
| All functions that allow users to specify color code are vulnerable to ReDoSAnalysed#511381 | Valid | Denial of Service | Low | 2019-08-21 | $1,000 | 53 |
| Clientside resource Exhausting by exploiting gitlab math renderingAnalysed#549040 | Valid | Denial of Service | Low | 2019-10-01 | – | 50 |
| Uncontrolled Resource Consumption in any Markdown field using MermaidAnalysed#670572 | Valid | Denial of Service | Medium | 2019-12-20 | – | 31 |
| DOS via issue previewAnalysed#1543718 | Valid | Denial of Service | High | 2022-11-04 | $7,640 | 25 |
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.