Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- Fix
- Fixed in 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
GitLab Community Edition and Enterprise Edition are affected. Under certain conditions, an unauthenticated attacker could read arbitrary files from the GitLab server through the repository commits API.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.
Timeline
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CVE published
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- GitLab GitLab
From 18.7 · fixed in 18.11.12; From 19.0 · fixed in 19.0.9; From 19.1 · fixed in 19.1.8; From 19.2 · fixed in 19.2.6; From 19.3 · fixed in 19.3.2