GitLab up to 19.3.8/19.4.7/19.5.5 Pages path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00+ |
Summary
A vulnerability, which was classified as problematic, has been found in GitLab up to 19.3.8/19.4.7/19.5.5. Affected by this issue is some unknown functionality of the component Pages. This manipulation causes path traversal. This vulnerability is tracked as CVE-2026-11768. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic was found in GitLab up to 19.3.8/19.4.7/19.5.5. Affected by this vulnerability is an unknown functionality of the component Pages. The manipulation with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality. The summary by CVE is:
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.4 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to read private CI/CD job artifacts belonging to other projects through GitLab Pages due to improper validation of file paths.
The advisory is shared at gitlab.com. This vulnerability is known as CVE-2026-11768 since 06/09/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Upgrading to version 19.3.9, 19.4.8 or 19.5.6 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 19.3.0
- 19.3.1
- 19.3.2
- 19.3.3
- 19.3.4
- 19.3.5
- 19.3.6
- 19.3.7
- 19.3.8
- 19.4.0
- 19.4.1
- 19.4.2
- 19.4.3
- 19.4.4
- 19.4.5
- 19.4.6
- 19.4.7
- 19.5.0
- 19.5.1
- 19.5.2
- 19.5.3
- 19.5.4
- 19.5.5
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.8
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: Path traversalCWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: GitLab 19.3.9/19.4.8/19.5.6
Timeline
06/09/2026 CVE reserved11/17/2026 Advisory disclosed
11/17/2026 VulDB entry created
11/17/2026 VulDB entry last update
Sources
Advisory: gitlab.comStatus: Confirmed
CNA: GitLab
CVE: CVE-2026-11768 (🔒)
GCVE (CVE): GCVE-0-2026-11768
GCVE (VulDB): GCVE-100-437977
Entry
Created: 11/17/2026 05:40Changes: 11/17/2026 05:40 (63)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.