Skip to content

Bug bounty reports15,219

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

Program:GitLab
Status
Severity
Weakness
Year:2019
Clear
Bounty paid4
Access stated
Access needed:No account
Technique
Clear filters9 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Full access to internal Gitlab instances at redash.gitlab.com, dashboards.gitlab.com, prometheus.gitlab.comAnalysed#498964ValidAccess ControlCritical2019-04-19–306
Unauthenticated blind SSRF in OAuth Jira authorization controllerAnalysed#398799ValidServer-Side Request ForgeryHigh2019-03-14$4,000238
Group search leaks private MRs, code, commitsAnalysed#692252ValidAccess ControlHigh2019-12-14–212
Snippet JS template allows attacker to read a user's private snippetsAnalysed#348443ValidInformation DisclosureLow2019-03-03$300165
information disclosure of secret_key_base via encoding charctersAnalysed#460545ValidInformation DisclosureHigh2019-06-13$3,500146
GraphQL query "namespace" leaks dataAnalysed#614355ValidAccess ControlMedium2019-12-03–64
Bypassing push rules via MRs created by EmailAnalysed#526570ValidAccess ControlMedium2019-10-01–36
Access Projects And create projects in gitlab pre production serverAnalysed#540711ValidAccess ControlLow2019-08-28–28
Claiming package names in GitLab's automatic package referencer.Analysed#462503ValidInput Validation and LogicLow2019-04-05$1,00026

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