An attacker could cause a Prometheus denial of service in GitLab 13.7+ by sending an HTTP request with a malformed method

In GitLab Enterprise Edition (EE) 12.5.0 through 12.7.5, sharing a group with a group could grant project access to unauthorized users.

GitLab EE 8.9 and later through 12.7.2 has Insecure Permission

GitLab 10.7 and later through 12.7.2 has Incorrect Access Control.

GitLab EE 8.9 and later through 12.7.2 has Insecure Permission

GitLab EE 12.6 and later through 12.7.2 allows Denial of Service.

GitLab EE 8.8 and later through 12.7.2 has Insecure Permissions.

GitLab EE 12.4 and later through 12.7.2 has Incorrect Access Control.

GitLab EE 10.1 through 12.7.2 allows Information Disclosure.

GitLab through 12.7.2 allows XSS.

GitLab EE 12.2 has Insecure Permissions (issue 2 of 2).

GitLab EE 11.0 and later through 12.7.2 allows XSS.

GitLab EE 8.0 and later through 12.7.2 allows Information Disclosure.

GitLab EE 8.0 through 12.7.2 has Incorrect Access Control.

GitLab EE 8.0 through 12.7.2 has Insecure Permissions (issue 1 of 2).

GitLab EE 11.11 and later through 12.7.2 allows Directory Traversal.

An issue was discovered in GitLab EE 11.3 and later. A GitLab Workhorse bypass could lead to package and file disclosure via request smuggling.

An issue was discovered in GitLab Enterprise Edition (EE) 8.9.0 through 12.6.1. Using the project import feature, it was possible for someone to obtain issues from private projects.

An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 5.1 through 12.6.1. It has Incorrect Access Control.

Information disclosure via GraphQL in GitLab CE/EE 13.1 and later exposes private group and project membership. This affects versions >=13.6 to <13.6.2, >=13.5 to <13.5.5, and >=13.1 to <13.4.7.