CVE-2026-0934: Incorrect Authorization in GitLab
GitLab has remediated an issue in GitLab EE affecting all versions from 17.9 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 with custom role permissions to view, create, or delete protected environment configurations despite CI/CD visibility being disabled for the project.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 18.11.6 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.0.3 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.1.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-0934?
The severity of CVE-2026-0934 is classified as low with a score of 3.8.
How do I fix CVE-2026-0934?
To fix CVE-2026-0934, upgrade GitLab to version 18.11.6 or later, 19.0.3 or later, or 19.1.1 or later.
What impact does CVE-2026-0934 have on GitLab users?
CVE-2026-0934 may allow authenticated users with custom role permissions to manipulate protected environment configurations.
Which versions of GitLab are affected by CVE-2026-0934?
CVE-2026-0934 affects GitLab EE versions from 17.9 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1.
Is authentication required to exploit CVE-2026-0934?
Yes, CVE-2026-0934 requires authentication as it involves an authenticated user with custom role permissions.