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

Medium 4.3 Published 25 Feb 2026 Updated 26 Feb 2026

Developers can bypass authorization to modify protected Conan packages in GitLab EE, requiring an upgrade to secure the platform.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2026-1747?

CVE-2026-1747 is a medium-severity authentication bypass vulnerability in Gitlab Gitlab, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

GitLab has remediated an issue in GitLab EE affecting all versions from 17.11 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that, under certain conditions, could have allowed Developer-role users with insufficient privileges to make unauthorized modifications to protected Conan packages.

Weakness: CWE-288

Which versions are affected by CVE-2026-1747?

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

Package	Affected	Fixed in
`gitlab` Bitnami	From `17.11.0`	`18.7.5, 18.8.5, 18.9.1`

Products include Gitlab Gitlab.

How do I fix CVE-2026-1747?

Upgrade gitlab to a fixed version for your release line: 18.7.5, 18.8.5 or 18.9.1.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-1747 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1747 exists.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-1747, GHSA-289q-cmj5-r43x, UBUNTU-CVE-2026-1747.