CVE-2026-15423: Incorrect Authorization in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute CI/CD pipelines on a protected branch without the required push permissions due to improper authorization in pipeline reference validation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.0.6 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.1.4 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.2.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-15423?
The severity of CVE-2026-15423 is rated high with a score of 8.5.
What is CVE-2026-15423 about?
CVE-2026-15423 pertains to incorrect authorization in GitLab that allows certain authenticated users to execute CI/CD pipelines on protected branches.
Which versions of GitLab are affected by CVE-2026-15423?
CVE-2026-15423 affects all versions of GitLab CE/EE from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2.
How do I fix CVE-2026-15423?
To fix CVE-2026-15423, upgrade GitLab to version 19.0.6, 19.1.4, or 19.2.2 or later.
What impact does CVE-2026-15423 have on GitLab users?
CVE-2026-15423 could allow authenticated users with developer-role permissions to bypass restrictions and execute potentially unauthorized CI/CD operations.