CVE-2026-85706
Received Received - Intake

Path Traversal in GitLab CE/EE via Repository Commits API

Vulnerability report for CVE-2026-85706, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-12

Last updated on: 2026-09-12

Assigner: GitLab Inc.

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-12
Last Modified
2026-09-12
Generated
2026-09-12
AI Q&A
2026-09-12
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
gitlab gitlab_ce From 18.7 (inc) to 19.1.8 (exc)
gitlab gitlab_ee From 18.7 (inc) to 19.1.8 (exc)
gitlab gitlab_ce From 19.2.0 (inc) to 19.2.6 (exc)
gitlab gitlab_ee From 19.2.0 (inc) to 19.2.6 (exc)
gitlab gitlab_ce From 19.3.0 (inc) to 19.3.2 (exc)
gitlab gitlab_ee From 19.3.0 (inc) to 19.3.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability allows an unauthenticated user to read arbitrary files from a GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API. It affects all GitLab CE/EE versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2.

Detection Guidance

This vulnerability allows unauthenticated file reads via the repository commits API. To detect it, check GitLab server logs for suspicious API requests targeting /api/v4/projects/:id/repository/commits. Look for unusual file paths in parameters. Verify GitLab version is updated to 19.1.8, 19.2.6, or 19.3.2 or later.

Impact Analysis

An attacker could exploit this to access sensitive files on the server, including configuration files, source code, or other confidential data. This could lead to data breaches, unauthorized access, or further attacks on the system.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR, HIPAA, or other regulations due to unauthorized data access. It may result in legal penalties, loss of trust, and reputational damage for organizations handling sensitive data.

Mitigation Strategies

Upgrade GitLab to a patched version: 19.1.8, 19.2.6, or 19.3.2 or later. Verify the upgrade was successful and monitor for unusual file access patterns.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-85706. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart