GitLab EE Auth Bypass in Protected Env <19.1.7/19.2.5/19.3.1 Improper Authorization
CVE-2026-3035 Published on August 26, 2026
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.
Vulnerability Analysis
CVE-2026-3035 can be exploited with network access, and requires user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have a small impact on confidentiality and integrity, and no impact on availability.
Weakness Type
Authentication Bypass Using an Alternate Path or Channel
A product requires authentication, but the product has an alternate path or channel that does not require authentication.
Products Associated with CVE-2026-3035
Want to know whenever a new CVE is published for GitLab? stack.watch will email you.
Affected Versions
GitLab:- Version 11.3 and below 19.1.7 is affected.
- Version 19.2 and below 19.2.5 is affected.
- Version 19.3 and below 19.3.1 is affected.