GitLab · disclosed reports
Information Disclosure
28 disclosed reports · $26,300 paid · 28 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
- 28
- valid
- 28
- paid a bounty
- 5
Every one of the 28 is a mark on the map. Named now: 1 to 26, most upvoted first.
- gitlab-workhorse bypass in Gitlab::Middleware::Multipart allowing files in `allowed_paths` to be read
- JSON serialization of any Project model results in all Runner tokens being exposed through Quick Actions
- Snippet JS template allows attacker to read a user's private snippets
- information disclosure of secret_key_base via encoding charcters
- Read files on application server, leads to RCE
- Able to view hackerone reports attachments
- Know whether private project name exists or not within a group using link comments
- EXIF metadata not stripped from JPG group logos
- Maintainer can leak sentry token by changing the configured URL (fix bypass)
- Able to leak private email of any user given his/her username via graphql
- Unauthorized access to private project security dashboard
- Last build status and coverage leaked to unauthorized users
- Unauthorized users may be able to view almost all informations related to Private projects.
- Race condition in GitLab import, giving access to other people their imports due to filename collision
- Private System Note Disclosure using GraphQL
- [information disclosure] Validate existence of a private project.
- SSRF when importing a project from a git repo by URL
- Users can download old project exports due to unclaimed namespace
- Boards leak private label names and desciptions
- Attacker can extract list of private project's project members
- Unauthorized user is able to access schedule pipeline variables and values
- Path paths and file disclosure vulnerabilities at influxdb.quality.gitlab.net
- Todos are not redacted when membership changes - Access to (confidential) issues and merge requests
- Private snippets in public / internal projects leaked though GitLab API
- Labels created in private projects are leaked
- GFM renderer leaks external issue tracker URL of private project
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.