CVE-2026-78335: Incorrect Authorization in GitLab
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 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 holding a project-scoped fine-grained Personal Access Token to modify integrations belonging to a group outside the token's scope, due to incorrect authorization checks.
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 are affected?
GitLab CE/EE is affected in versions 19.1 through before 19.2.8, 19.3 through before 19.3.5, and 19.4 through before 19.4.2.
What does an attacker need to exploit this issue?
An attacker needs to be authenticated and possess a project-scoped fine-grained Personal Access Token. Exploitation also requires the conditions under which the incorrect authorization checks permit modification of an integration in a group outside that token's scope.
What is the impact of successful exploitation?
A successful attacker could modify integrations belonging to a group that is outside the scope of their project-scoped fine-grained Personal Access Token. The reported impact includes limited confidentiality and integrity effects, with no availability impact indicated.
Which versions address the issue?
The issue is remediated in GitLab 19.2.8, 19.3.5, and 19.4.2.