GitLab · disclosed reports
Access Control
15 disclosed reports · $52,160 paid · 15 valid
Every dot is a report; the named ones are the most upvoted. Bright dots were paid a bounty. A report opens its page here: our analysis where there is one, and the link to HackerOne. The status is HackerOne's own outcome; "access needed" is only what a title states.
Open GitLab on HackerOne- reports
- 15
- valid
- 15
- paid a bounty
- 6
Every one of the 15 is a mark on the map. Named now: 1 to 15, most upvoted first.
- Exfiltrate and mutate repository and project data through injected templated service
- Project Template functionality can be used to copy private project data, such as repository, confidential issues, snippets, and merge requests
- Attacker is able to access commit title and team member comments which are supposed to be private
- Privilege escalation from any user (including external) to gitlab admin when admin impersonates you
- Group search with Elastic search enable leaks unrelated data
- RepositoryPipeline allows importing of local git repos
- Privilege escalation of "external user" (with maintainer privilege) to internal access through project token
- Ability to access all user authentication tokens, leads to RCE
- Improper access control for users with expired password, giving the user full access through API and Git
- Guest users can create new test cases
- A deactivated user can access data through GraphQL
- Milestones leaked via search API
- Kroki Arbitrary File Read/Write
- Privilege escalation due to insecure use of logrotate
- Guest Users can create issues for Sentry errors and track their status
paid a bounty
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.