Authenticated code execution via package-registry path traversal
Published Aug 23, 2026 · Updated Aug 25, 2026
Path traversal in GitLab CE/EE 18.8 through 19.2 allows remote authenticated users to execute code through the package registry. GitLab identifies the package registry as the locus but has not disclosed which pathname is attacker-controlled or how traversal reaches code execution. Exploitation requires an authenticated account and unspecified high-complexity conditions; successful attacks compromise the GitLab server.
Summary
What happened
Path traversal in GitLab CE/EE 18.8 through 19.2 allows remote authenticated users to execute code through the package registry. GitLab identifies the package registry as the locus but has not disclosed which pathname is attacker-controlled or how traversal reaches code execution. Exploitation requires an authenticated account and unspecified high-complexity conditions; successful attacks compromise the GitLab server.
The record
- CVE
- CVE-2026-10053
- Published
- Aug 23, 2026
- Updated
- Aug 25, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 23, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=18.8 <19.0.6
- Affected versionversion=19.1 <19.1.4
- Affected versionversion=19.2 <19.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo