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

What is CVE-2026-5309?

CVE-2026-5309 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 25 Jun 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 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user to read or modify another group's virtual registry cleanup policy settings without authorization.

Weakness: CWE-639

Which versions are affected by CVE-2026-5309?

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

Products include Gitlab Gitlab.

How do I fix CVE-2026-5309?

Upgrade gitlab to a fixed version for your release line: 18.11.6, 19.0.3 or 19.1.1.

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

Is CVE-2026-5309 being exploited?

There is no known exploitation of CVE-2026-5309 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-5309, GHSA-r9m9-87p7-xj9f.