CVE-2026-6063 Authorization Bypass Through User-Controlled Key in GitLab

What is CVE-2026-6063?

CVE-2026-6063 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

GitLab has remediated an issue in GitLab EE affecting all versions from 11.10 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that under certain conditions could have allowed an authenticated user with developer-role permissions to remove code owner approval rules from merge requests due to improper access control.

Weakness: CWE-639

Which versions are affected by CVE-2026-6063?

1 open source package ship an affected version, including gitlab. It affects 1 product.

Products include Gitlab Gitlab.

How do I fix CVE-2026-6063?

Upgrade gitlab to a fixed version for your release line: 18.9.7, 18.10.6 or 18.11.3.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-6063 being exploited?

There is no known exploitation of CVE-2026-6063 in the wild and no public exploit code.

Other vulnerabilities in Gitlab Gitlab

• CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound Exploited Critical 10.0
• CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal Exploited Critical 10.0
• CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control Exploited Critical 10.0
• CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution Exploited Critical 10.0
• CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) Exploited Medium 6.8

All Gitlab Gitlab vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as BIT-gitlab-2026-6063, GHSA-57q4-65mf-59mf, UBUNTU-CVE-2026-6063.