8.5High
Gitlab Gitlab
CVE-2026-10053
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.
What this means for your business
- It affects Gitlab. It matters if your company, or a supplier that handles your data, runs it.
- An attacker can use it remotely, over a network, with an ordinary user login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 0.8% chance of attack attempts being seen in the next 30 days, ranking above 53% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Gitlab, and which version. The affected versions are listed further down this page.
- 2If you do, follow the vendor's guidance. No patch reference has been published yet.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 8.5 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H- Weakness
- CWE-22
- Assigned by
- cve@gitlab.com
Dates
- Published
- 2026-08-23
- Last modified
- 2026-08-31
- Sources
- NVD
Affected products
- Gitlab Gitlab18.8.0 - 19.0.6, 19.1.0 - 19.1.4, 19.2.0 - 19.2.2
As listed in the NVD configuration data. Not a statement about your estate.