CVE-2026-82632: Incorrect Authorization in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user with a fine-grained Personal Access Token scoped only to user-boundary import permissions to import projects into group namespaces beyond the token's intended scope, due to incorrect authorization of the import target namespace.
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.2.8 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.3.5 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 19.4.2
Event History
Frequently Asked Questions
Which deployments need remediation?
GitLab CE/EE deployments are affected if they run a version from 18.9 before 19.2.8, 19.3 before 19.3.5, or 19.4 before 19.4.2.
What does an attacker need to exploit this issue?
The attacker must be authenticated and possess a fine-grained Personal Access Token limited to user-boundary import permissions. Exploitation also depends on the stated unspecified conditions being present.
What unauthorized action could occur?
A qualifying token could be used to import projects into group namespaces that are outside the token's intended scope.
Which fixed releases address the issue?
The remediation is available in GitLab 19.2.8, 19.3.5, and 19.4.2.