CVE-2026-14341: Missing Authorization in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with Maintainer role to modify protected branch configuration due to improper authorization in a projects API endpoint.
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.5 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.1.3 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.2.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-14341?
The severity of CVE-2026-14341 is medium with a score of 4.9.
How do I fix CVE-2026-14341?
To fix CVE-2026-14341, upgrade GitLab to versions 19.0.5, 19.1.3, or 19.2.1 or later.
What can attackers do with CVE-2026-14341?
Attackers with an authenticated Maintainer role could modify protected branch configurations due to improper authorization under certain conditions.
Which versions of GitLab are affected by CVE-2026-14341?
CVE-2026-14341 affects GitLab CE/EE versions from 12.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1.
Who is impacted by CVE-2026-14341?
Authenticated users with the Maintainer role in GitLab could be impacted by CVE-2026-14341.