Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
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.
- Published
- Sep 11, 2026
- Updated
- Sep 24, 2026
- EPSS
- 91.4% · 100th percentile▲ 82
- CWE
- CWE-22
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
97
Now
Patch today or shut off access.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 27 / 30 · 91.4%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitLab
- 10.0
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Sep 11, 2026. That signals real attacks, not theory.
Remediation deadline for government agencies: Sep 14, 2026.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| gitlab | gitlab | cpe:2.3:a:gitlab:gitlab |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gitlab gitlab18.7.0 and later · before 18.11.12
- gitlab gitlab19.0.0 and later · before 19.0.9
- gitlab gitlab19.1.0 and later · before 19.1.8
- gitlab gitlab19.2.0 and later · before 19.2.6
- gitlab gitlab19.3.0 and later · before 19.3.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitLab). Independent of NVD's CPE analysis and usually ahead of it.
GitLab GitLab
- 18.7 and later · before 18.11.12affected · semver
- 19.0 and later · before 19.0.9affected · semver
- 19.1 and later · before 19.1.8affected · semver
- 19.2 and later · before 19.2.6affected · semver
- 19.3 and later · before 19.3.2affected · semver
Same product
gitlab: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-22205An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9.KEV100Now
- CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV97Now
- CVE-2021-22175When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab affecting all versionsKEV85Now
- CVE-2021-39935An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.5 before 14.3.6, all versions starting from 14.4 beforeKEV71This week
- CVE-2022-2992A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows an authenticated us65This week
- CVE-2022-2884A vulnerability in GitLab CE/EE affecting all versions from 11.3.4 prior to 15.1.5, 15.2 to 15.2.3, 15.3 to 15.3 to 15.3.1 allows an an auth62This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| GitLab GitLab | 18.11.12 | Vendor (CNA) |
| GitLab GitLab | 19.0.9 | Vendor (CNA) |
| GitLab GitLab | 19.1.8 | Vendor (CNA) |
| GitLab GitLab | 19.2.6 | Vendor (CNA) |
| GitLab GitLab | 19.3.2 | Vendor (CNA) |
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×13
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | auxiliary/gather/gitlab_file_read_cve_2026_85706GitLab Unauthenticated Arbitrary File Readauxiliary | 2026-09-10 |
| Nuclei detection template | Nuclei template CVE-2026-85706 | — |
| Proof-of-concept repository on GitHub | stars:2 | 2026-09-11 |
| Proof-of-concept repository on GitHub | stars:42 | 2026-09-11 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-11 |
| Proof-of-concept repository on GitHub | stars:12 | 2026-09-11 |
| Proof-of-concept repository on GitHub | stars:8 | 2026-09-11 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-09-12 |
| Proof-of-concept repository on GitHub | stars:4 | 2026-09-12 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-13 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-09-13 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-09-14 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-2 d
- First PoC-1 d
- CISA KEV-1 d
- Published
- TodaySep 29, 2026+18 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1005319 days apartImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab35Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-877190 days apartDeserialization of Untrusted Data in GitLab39Monitor
- CVE-2026-9357712 days apartInteger Overflow or Wraparound in GitLab39Monitor
- CVE-2026-887654 days apartImproper Neutralization of Special Elements used in a Command ('Command Injection') in GitLab34Monitor
- CVE-2026-167945 days apartMissing Authorization in GitLab17Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
nvd-secondary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) { return res.sendStatus(400);}res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- gitlab.com/gitlab-org/gitlab/-/work_items/627748
- hackerone.com/reports/3909881
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-85706
Vendor advisories and official records. Exploit/PoC links are deliberately left out.