CVE-2026-3035 Authentication Bypass Using an Alternate Path or Channel in GitLab

Medium 5.5 Published 26 Aug 2026 Updated 26 Aug 2026

Authenticated Maintainers can bypass authorization checks to access protected environment terminals, potentially leading to code execution.

Exploited in the wild: Not known
Login needed: An administrator
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2026-3035?

CVE-2026-3035 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 26 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

Official 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.

Weakness: CWE-288

Which versions are affected by CVE-2026-3035?

1 open source package ship an affected version, including gitlab. It affects 1 product.

Package	Affected	Fixed in
`gitlab` Bitnami	From `11.3.0`	`19.1.7, 19.2.5, 19.3.1`

Products include Gitlab Gitlab.

How do I fix CVE-2026-3035?

Upgrade gitlab to a fixed version for your release line: 19.1.7, 19.2.5 or 19.3.1.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-3035 being exploited?

There is no known exploitation of CVE-2026-3035 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-3035, GHSA-46vv-8gc3-7xrq, MINI-67pp-8f8p-6972, MINI-gpm5-v8wp-5g9c, MINI-jch9-c69j-c3m6.