CVE-2026-3035: Authentication Bypass Using an Alternate Path or Channel in GitLab
GitLab has remediated an issue in GitLab EE affecting all versions from 11.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with project Maintainer permissions could have accessed the terminal of a protected environment they were not authorized to use 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.1.7 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.2.5 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.3.1
Event History
Frequently Asked Questions
Who can exploit this issue?
Exploitation requires an authenticated GitLab EE user with Maintainer permissions on a project. The issue applies only under certain conditions involving protected environments.
What access could an attacker gain?
A qualifying project Maintainer could access the terminal of a protected environment that they were not authorized to use. The reported impact includes low confidentiality and integrity impact, with no availability impact.
Which releases are affected and which releases contain the fix?
Affected releases are all GitLab EE versions from 11.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1. Updating to 19.1.7, 19.2.5, or 19.3.1, as applicable to the release line, remediates the issue.