GitLab Community Edition/Enterprise Edition up to 18.10.7/18.11.4/19.0.1 File authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 18.10.7/18.11.4/19.0.1. It has been classified as problematic. Impacted is an unknown function of the component File Handler. This manipulation causes authorization. This vulnerability is registered as CVE-2026-6976. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 18.10.7/18.11.4/19.0.1. It has been declared as problematic. Affected by this vulnerability is an unknown code block of the component File Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to hide changes from merge request diff views due to improper input handling of file names.
The weakness was published by xorz. It is possible to read the advisory at gitlab.com. This vulnerability is known as CVE-2026-6976 since 04/24/2026. The exploitation appears to be difficult. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 18.10.8, 18.11.5 or 19.0.2 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
- 18.10.0
- 18.10.1
- 18.10.2
- 18.10.3
- 18.10.4
- 18.10.5
- 18.10.6
- 18.10.7
- 18.11.0
- 18.11.1
- 18.11.2
- 18.11.3
- 18.11.4
- 19.0.0
- 19.0.1
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (GitLab): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 18.10.8/18.11.5/19.0.2
Timeline
04/24/2026 CVE reserved06/11/2026 Advisory disclosed
06/11/2026 VulDB entry created
06/11/2026 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: gitlab.com
Researcher: xorz
Status: Confirmed
CVE: CVE-2026-6976 (🔒)
GCVE (CVE): GCVE-0-2026-6976
GCVE (VulDB): GCVE-100-370375
Entry
Created: 06/11/2026 16:22Changes: 06/11/2026 16:22 (66)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.