GitLab · disclosed reports
Information Disclosure
8 disclosed reports · $22,500 paid · 8 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
- 8
- valid
- 8
- paid a bounty
- 3
Every one of the 8 is a mark on the map. Named now: 1 to 8, 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
- Know whether private project name exists or not within a group using link comments
- EXIF metadata not stripped from JPG group logos
- Able to leak private email of any user given his/her username via graphql
- Unauthorized access to private project security dashboard
- 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
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-15 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.