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.
Published: 2026-08-23
Score: 8.5 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a path traversal flaw in GitLab’s package registry that allows an authenticated user to access files outside the intended directory. This can lead to remote code execution by allowing a malicious repository to contain a crafted file that the server will interpret as executable code. The flaw is categorized as CWE-22 and was present in all GitLab CE/EE releases from 18.8 up to, but not including, 19.0.6, 19.1.4, and 19.2.2.

Affected Systems

GitLab Community Edition and Enterprise Edition users who have installed versions 18.8 or 18.9 and any 19.0, 19.1, or 19.2 releases that are earlier than 19.0.6, 19.1.4, and 19.2.2 respectively. These versions are vulnerable if the package registry feature is enabled and require correction.

Risk and Exploitability

The CVSS base score is 8.5, indicating a high severity. EPSS data is not available, so the likelihood of exploitation cannot be precisely quantified. The vulnerability is not listed in CISA’s KEV catalog. Attackers need authenticated access to the GitLab instance and the ability to create or modify packages in the registry. Once the path traversal is exploited, they can achieve remote code execution on the host that runs GitLab.

Generated by OpenCVE AI on August 23, 2026 at 10:20 UTC.

Remediation

Vendor Solution

Upgrade to versions 19.0.6, 19.1.4, 19.2.2 or above.


OpenCVE Recommended Actions

  • Upgrade to GitLab version 19.0.6 or newer for the 19.0 line, 19.1.4 or newer for 19.1, and 19.2.2 or newer for 19.2.
  • If an immediate upgrade is not possible, disable or restrict access to the package registry feature for untrusted users.
  • Implement or verify input validation to ensure that pathnames are confined to the intended directory, and monitor logs for unauthorized file access attempts that may indicate exploitation.

Generated by OpenCVE AI on August 23, 2026 at 10:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 23 Aug 2026 09:30:00 +0000

Type Values Removed Values Added
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.
Title Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-22
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

{'score': 8.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-08-23T09:27:01.138Z

Reserved: 2026-05-29T07:34:04.473Z

Link: CVE-2026-10053

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-23T10:16:27.140

Modified: 2026-08-23T10:16:27.140

Link: CVE-2026-10053

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-23T10:30:04Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')