CVE-2026-92529: Incorrect Authorization in GitLab
GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to bypass admin-configured AI tool governance controls for workflows in namespaces they do not control due to improper authorization checks.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.2.7 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.3.3 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.4.1
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated GitLab EE user with the Developer role could exploit it, but only under certain conditions. The affected workflows are in namespaces the user does not control.
What is the practical impact of successful exploitation?
A Developer-role user could bypass administrator-configured AI tool governance controls for affected workflows. The reported impact is limited to integrity; no confidentiality or availability impact is specified.
Which GitLab EE versions need remediation?
Affected releases are all 19.1 versions before 19.2.7, all 19.3 versions before 19.3.3, and all 19.4 versions before 19.4.1. Upgrade to 19.2.7, 19.3.3, 19.4.1, or a later release in the applicable version line.