Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
4.3
CVE-2026-1747: GitLab developers may alter protected Conan packages
CVE-2026-1747 · published 8 months ago
Summary
In certain versions of GitLab, users with a developer role could bypass normal checks and change protected Conan packages they shouldn't edit. This could let them modify or replace code components used in builds. Update GitLab to the latest release or apply the provided patches to close the gap.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| gitlab | gitlab |
>= 17.11.0, < 18.7.5 >= 18.8.0, < 18.8.5 18.9.0 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:* |
Original advisory text
Authentication Bypass Using an Alternate Path or Channel in GitLab
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.
References
- https://about.gitlab.com/releases/2026/02/25/patch-release-gitlab-18-9-1-release... URL
- https://gitlab.com/gitlab-org/gitlab/-/issues/588385 Third Party Advisory
- https://hackerone.com/reports/3533088 Third Party Advisory
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/1xxx/CVE-2026-1747.j... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-1747 Vendor Advisory
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Type
CWE-288Authentication Bypass Using Alternate Path
Timeline
Published25 Feb 2026
Updated4 Nov 2026
First seen6 Mar 2026
Track software like this
Free during beta