CVE-2026-1747

Received Received - Intake

Privilege Escalation in GitLab EE Allows Unauthorized Package Modification

Publication date: 2026-02-25

Last updated on: 2026-02-28

Assigner: GitLab Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-02-25

Last Modified

2026-02-28

Generated

2026-07-06

AI Q&A

2026-02-25

EPSS Evaluated

2026-07-05

NVD

CVE-2026-1747

EUVD

EUVD-2026-8724

Affected Vendors & Products

Vendor	Product	Version / Range
gitlab	gitlab	From 18.8.0 (inc) to 18.8.5 (exc)
gitlab	gitlab	From 18.8.0 (inc) to 18.8.5 (exc)
gitlab	gitlab	18.9.0
gitlab	gitlab	18.9.0
gitlab	gitlab	From 17.11.0 (inc) to 18.7.5 (exc)
gitlab	gitlab	From 17.11.0 (inc) to 18.7.5 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-288	The product requires authentication, but the product has an alternate path or channel that does not require authentication.

Attack-Flow Graph

Executive Summary

This vulnerability in GitLab EE affects versions from 17.11 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1. Under certain conditions, it could allow users with the Developer role, who normally have limited privileges, to make unauthorized changes to protected Conan packages.

Impact Analysis

The impact of this vulnerability is that Developer-role users could modify protected Conan packages without proper authorization. This could lead to unauthorized changes in package contents, potentially compromising the integrity and reliability of software dependencies managed through GitLab.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

To mitigate this vulnerability, you should upgrade GitLab EE to a fixed version. Specifically, update to version 18.7.5 or later if you are on the 17.11 to before 18.7.5 range, to 18.8.5 or later if you are on 18.8 before 18.8.5, or to 18.9.1 or later if you are on 18.9 before 18.9.1.

Hi! I’m here to help you understand CVE-2026-1747. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70