CVE-2026-10053 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab

High 8.5 Published 23 Aug 2026 Updated 25 Aug 2026

An authenticated user can achieve remote code execution via a path traversal vulnerability in the GitLab package registry.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2026-10053?

CVE-2026-10053 is a high-severity path traversal vulnerability in Gitlab Gitlab, published on 23 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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.

Weakness: CWE-22

Which versions are affected by CVE-2026-10053?

1 open source package ship an affected version, including gitlab. It affects 1 product.

Package	Affected	Fixed in
`gitlab` Bitnami	From `18.8.0`	`19.0.6, 19.1.4, 19.2.2`

Products include Gitlab Gitlab.

How do I fix CVE-2026-10053?

Upgrade gitlab to a fixed version for your release line: 19.0.6, 19.1.4 or 19.2.2.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-10053 being exploited?

There is no known exploitation of CVE-2026-10053 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-10053, GHSA-2fpv-gqh2-qq5r, MINI-fr78-x77f-q5fw, MINI-mcxw-c3qx-xrc8.