CVE-2026-10053
Received Received - Intake

Path Traversal in GitLab CE/EE Package Registry

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

Publication date: 2026-08-23

Last updated on: 2026-08-23

Assigner: GitLab Inc.

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.8 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to achieve remote code execution due to a path traversal vulnerability in the package registry.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

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

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
gitlab gitlab_ce From 18.8 (inc) to 19.0.6 (exc)
gitlab gitlab_ee From 18.8 (inc) to 19.0.6 (exc)
gitlab gitlab_ce From 19.1.0 (inc) to 19.1.4 (exc)
gitlab gitlab_ee From 19.1.0 (inc) to 19.1.4 (exc)
gitlab gitlab_ce From 19.2.0 (inc) to 19.2.2 (exc)
gitlab gitlab_ee From 19.2.0 (inc) to 19.2.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 in GitLab CE/EE versions before 19.0.6, 19.1.4, and 19.2.2 allows an authenticated user to execute remote code due to a path traversal flaw in the package registry. The issue arises from improper path validation when handling package files.

Detection Guidance

Check GitLab version against affected releases (18.8 before 19.0.6, 19.1 before 19.1.4, 19.2 before 19.2.2). Inspect package registry logs for unusual file access patterns or path traversal attempts.

Impact Analysis

An attacker with valid credentials could exploit this to run arbitrary code on the server, potentially stealing data, installing malware, or disrupting services. The high CVSS score (8.5) indicates significant risk.

Compliance Impact

The vulnerability allows authenticated users to achieve remote code execution via path traversal in the package registry. This could lead to unauthorized access, data breaches, or manipulation of sensitive data, which may violate GDPR (data protection) and HIPAA (health data security) requirements depending on the affected system's use case.

Mitigation Strategies

Upgrade GitLab to patched versions (19.0.6, 19.1.4, or 19.2.2). Restrict authenticated user permissions and monitor package registry activity for suspicious behavior.

Chat Assistant

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

EPSS Chart