CVE-2026-2104
Authorization Bypass in GitLab CE/EE Allows Confidential Data Access
Publication date: 2026-04-08
Last updated on: 2026-04-14
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.9.0 (inc) to 18.9.5 (exc) |
| gitlab | gitlab | From 18.10.0 (inc) to 18.10.3 (exc) |
| gitlab | gitlab | From 18.2.0 (inc) to 18.8.9 (exc) |
| gitlab | gitlab | From 18.10.0 (inc) to 18.10.3 (exc) |
| gitlab | gitlab | From 18.9.0 (inc) to 18.9.5 (exc) |
| gitlab | gitlab | From 18.2.0 (inc) to 18.8.9 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GitLab CE/EE versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 allows an authenticated user to access confidential issues assigned to other users. The issue arises due to insufficient authorization checks during the CSV export process.
How can this vulnerability impact me? :
The vulnerability could lead to unauthorized disclosure of confidential issues within GitLab projects. An authenticated user might gain access to sensitive information assigned to other users, potentially exposing private or sensitive project details.
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.8.9 or later if you are on the 18.8 branch, 18.9.5 or later if on the 18.9 branch, or 18.10.3 or later if on the 18.10 branch.
This will ensure that the insufficient authorization checks allowing authenticated users to access confidential issues via CSV export are resolved.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability could allow an authenticated user to access confidential issues assigned to other users via CSV export due to insufficient authorization checks.
Such unauthorized access to confidential information may lead to non-compliance with data protection regulations like GDPR and HIPAA, which require strict controls over access to sensitive data.