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… (CVE-2026-10053)
A path traversal vulnerability in GitLab CE/EE versions from 18.8 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 could allow an authenticated user to achieve remote code execution. This issue affects the package registry component and has been remediated in the specified fixed versions.
AI Analysis
Technical Summary
CVE-2026-10053 is a path traversal vulnerability in GitLab Community and Enterprise Editions affecting versions from 18.8 up to but not including 19.0.6, 19.1 up to but not including 19.1.4, and 19.2 up to but not including 19.2.2. Under certain conditions, an authenticated user could exploit this vulnerability in the package registry to execute remote code. The vulnerability is classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory). The CVSS v3.1 base score is 8.5, indicating high severity with network attack vector, high impact on confidentiality, integrity, and availability, and requiring low privileges with high attack complexity.
Potential Impact
Successful exploitation allows an authenticated user to execute arbitrary code remotely on the affected GitLab server, potentially compromising confidentiality, integrity, and availability of the system. This could lead to full system compromise depending on the privileges of the exploited process.
Mitigation Recommendations
The vulnerability has been officially fixed by GitLab in versions 19.0.6, 19.1.4, and 19.2.2. Users should upgrade affected GitLab CE/EE instances to these or later versions to remediate the issue. No additional mitigation steps are indicated beyond applying these official patches.
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… (CVE-2026-10053)
Description
A path traversal vulnerability in GitLab CE/EE versions from 18.8 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 could allow an authenticated user to achieve remote code execution. This issue affects the package registry component and has been remediated in the specified fixed versions.
CVSS v3.1
Score 8.5high
Affected software
pkg:gem/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-10053 is a path traversal vulnerability in GitLab Community and Enterprise Editions affecting versions from 18.8 up to but not including 19.0.6, 19.1 up to but not including 19.1.4, and 19.2 up to but not including 19.2.2. Under certain conditions, an authenticated user could exploit this vulnerability in the package registry to execute remote code. The vulnerability is classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory). The CVSS v3.1 base score is 8.5, indicating high severity with network attack vector, high impact on confidentiality, integrity, and availability, and requiring low privileges with high attack complexity.
Potential Impact
Successful exploitation allows an authenticated user to execute arbitrary code remotely on the affected GitLab server, potentially compromising confidentiality, integrity, and availability of the system. This could lead to full system compromise depending on the privileges of the exploited process.
Mitigation Recommendations
The vulnerability has been officially fixed by GitLab in versions 19.0.6, 19.1.4, and 19.2.2. Users should upgrade affected GitLab CE/EE instances to these or later versions to remediate the issue. No additional mitigation steps are indicated beyond applying these official patches.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2fpv-gqh2-qq5r
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-10053"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a8af99cacd9273b49f32da5
Added to database: 08/23/2026, 13:46:04 UTC
Last enriched: 08/23/2026, 13:46:47 UTC
Last updated: 08/24/2026, 01:09:50 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.