Skip to content

Bug bounty reports15,219

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

Program:GitLab
Status
Severity
Weakness:Authentication
Clear
Year
Bounty paid3
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters9 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Ability to bypass email verification for OAuth grants results in accounts takeovers on 3rd partiesAnalysed#922456ValidAuthenticationHigh2020-10-01$3,000257
Mint Oauth2 access token for targeted userAnalysed#1148364ValidAuthenticationHigh2025-07-23$5,580140
Login email verification bypass via `/oauth/token`.#2676025InformativeAuthenticationNone2024-09-03–66
Access to GitLab's Slack by abusing issue creation from e-mailAnalysed#218230ValidAuthenticationCritical2017-09-21–54
Exposure of a valid Gitlab-Workhorse JWT leading to various bad thingsAnalysed#1040786ValidAuthenticationHigh2022-07-05$10,00036
Remote hacker can download all the files of master branch in public projects where everything is members only.Analysed#1043480ValidAuthenticationMedium2021-02-15–31
Bypassing password authentication of users that have 2FA enabledAnalysed#128085ValidAuthentication–2016-04-18–27
Inadequate cache control in gitter allows to view private chat room#493791DuplicateAuthenticationNone2019-03-08–13
Last pipeline status for MR leaked#582349ValidAuthenticationLow2019-10-01–10

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.