CVE-2026-6713
GitLab CE/EE Private Project Enumeration Vulnerability
Publication date: 2026-05-27
Last updated on: 2026-05-27
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.11.0 (inc) to 18.11.4 (exc) |
| gitlab | gitlab | 19.0.0 |
| gitlab | gitlab | From 18.11.0 (inc) to 18.11.4 (exc) |
| gitlab | gitlab | From 18.2.0 (inc) to 18.10.7 (exc) |
| gitlab | gitlab | From 18.2.0 (inc) to 18.10.7 (exc) |
| gitlab | gitlab | 19.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GitLab CE/EE versions before certain fixed releases allowed an unauthorized user to enumerate private projects. The issue was caused by incorrect authorization checks under certain conditions.
How can this vulnerability impact me? :
The impact of this vulnerability is that an unauthorized user could discover the existence of private projects that they should not have access to. This could lead to information disclosure about private projects, although it does not allow modification or deletion of data.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade GitLab CE/EE to a fixed version. Specifically, update to version 18.10.7 or later if you are using the 18.2 to 18.10 series, version 18.11.4 or later if you are using the 18.11 series, or version 19.0.1 or later if you are using the 19.0 series.