CVE-2026-3035

Authentication Bypass Using an Alternate Path or Channel in GitLab

Published Aug 26, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability is an authentication bypass using an alternate path that allows a user with project Maintainer permissions to access the terminal of a protected environment they are not authorized to use. This unauthorized access can enable the attacker to execute commands within the environment, potentially compromising confidentiality and integrity of the affected system. The weakness is a failure of proper authorization checks, classified as CWE-288.

Affected Systems

The affected product is GitLab Enterprise Edition as distributed by GitLab, with all releases from 11.3 up to but excluding 19.1.7, from 19.2 up to but excluding 19.2.5, and from 19.3 up to but excluding 19.3.1. These versions are legacy builds that remain in many organizations' environments.

Risk and Exploitability

The CVSS score of 5.5 indicates moderate severity, and the EPSS score is not available, but the vulnerability is not listed in the CISA KEV catalog. Exploitation requires an authenticated user with Maintainer privileges and knowledge of the target environment; no special privileges beyond project authorization are needed. Because the attacker can gain terminal access, the risk includes remote code execution and privilege escalation within the protected environment.

Remediation

Vendor Solution

Upgrade to versions 19.1.7, 19.2.5, 19.3.1 or above.


OpenCVE Recommended Actions

  • Upgrade GitLab EE to version 19.1.7, 19.2.5, 19.3.1 or later to apply the fix.
  • Restrict Maintainer permissions to prevent terminal access to protected environments if tighter controls are required.
  • Enable logging of terminal usage to detect any unauthorized activity.

Generated by OpenCVE AI on August 26, 2026 at 14:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
cpe:2.3:a:gitlab:gitlab:19.3.0:*:*:*:enterprise:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Authentication Bypass Using an Alternate Path or Channel in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-288
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N'}

Weaknesses
  • CWE-288

    Authentication Bypass Using an Alternate Path or Channel

Sources

Status
PUBLISHED
Assigner
GitLab
Published
Updated
Aug 26, 2026, 3:41 PM
Reserved
Feb 23, 2026, 4:06 PM
Status
Analyzed
Published
Aug 26, 2026, 2:17 PM
Modified
Aug 31, 2026, 3:42 PM