CVE-2026-85706
GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
Description
CVE-2026-85706 is a critical path traversal vulnerability in GitLab Community Edition and Enterprise Edition that allows an unauthenticated user to read arbitrary files from the GitLab server. The flaw sits in the repository commits API, where improper path confinement combines with missing authentication enforcement, so a crafted request can escape the intended repository directory and return files from elsewhere on the host. GitLab CE/EE is affected in all versions from 18.7 before 19.1.8, 19.2 before 19.2.6 and 19.3 before 19.3.2. With a maximum CVSS score of 10.0 and inclusion in the CISA Known Exploited Vulnerabilities (KEV) catalog, CVE-2026-85706 is an immediate-action vulnerability for anyone running a self-managed GitLab instance.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NOpen in CalculatorAffected Products
| Vendor | Product | Version |
|---|---|---|
| gitlab | gitlab | >= 18.7.0, < 18.11.12; >= 19.0.0, < 19.0.9; >= 19.1.0, < 19.1.8; >= 19.2.0, < 19.2.6; >= 19.3.0, < 19.3.2 |
References
- https://gitlab.com/gitlab-org/gitlab/-/work_items/627748(Broken Link)
- https://hackerone.com/reports/3909881(Permissions Required)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-85706(Third Party Advisory, US Government Resource)
Weakness Type
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Path traversal occurs when software builds a file path from external input but fails to neutralise sequences such as "../" that let the resulting path resolve outside the restricted parent directory. In CVE-2026-85706 the GitLab repository commits API accepts attacker-influenced path data without proper confinement, so the file lookup escapes the repository storage directory and reads arbitrary files from the GitLab server's filesystem.
Learn more: CWE-22 — Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Impact Analysis
CVE-2026-85706 reaches the maximum CVSS 3.1 base score of 10.0 because it is remotely exploitable over the network with low attack complexity, no authentication and no user interaction, and because its scope is CHANGED — the attack affects resources beyond the vulnerable component, reading files belonging to the underlying host rather than only to the targeted repository. Confidentiality and integrity impacts are both High, so an attacker can retrieve secrets such as GitLab configuration files, database credentials, secret keys and CI/CD variables, and leverage what they find to alter the state of the instance; availability is not directly impacted. For a self-managed GitLab server the practical consequence is severe, because the secrets stored on that host typically unlock the source code, pipelines and deployment credentials of the entire organisation. The EPSS score of roughly 1.1% (65th percentile) is a lagging indicator here — CISA's KEV listing confirms real exploitation, and a HackerOne report referenced by GitLab shows the technique is documented outside the vendor.
Exploit Maturity
CISA has confirmed active exploitation of CVE-2026-85706 by adding it to the Known Exploited Vulnerabilities catalog with a 14 September 2026 remediation deadline, so self-managed GitLab instances should be treated as under attack. GitLab's advisory references a HackerOne report and a public GitLab work item, meaning technical detail about the vulnerable commits API path is available outside the vendor and reduces the effort required to reproduce the issue. The EPSS score of about 1.1% (65th percentile) does not reflect that reality, as EPSS responds slowly to newly weaponised enterprise vulnerabilities. The KEV ransomware flag is "Unknown", but an unauthenticated arbitrary file read on a source-code platform is an unusually attractive target, and defenders should assume exploitation attempts are ongoing.
Remediation
- Follow the CISA KEV required action. Apply mitigations in accordance with GitLab's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV due date is 14 September 2026.
- Upgrade GitLab CE/EE immediately to 19.1.8, 19.2.6 or 19.3.2 or later. All versions from 18.7 up to those builds are affected; pick the patch release matching your current major.minor line and apply it before any other hardening step, since no configuration change removes the underlying path traversal.
- Rotate every secret reachable from the GitLab host. Assume arbitrary file read succeeded: rotate the GitLab secrets file and database credentials, reissue runner registration tokens, personal and project access tokens, CI/CD variables, deploy keys and any cloud credentials stored on the instance.
- Hunt for indicators of compromise in the commits API logs. Review GitLab and reverse-proxy access logs for requests to repository commits endpoints containing traversal sequences or unusual path parameters, especially unauthenticated requests, and correlate with unexpected reads of configuration paths.
- Reduce exposure and harden path handling long term by placing self-managed GitLab behind a VPN or IP allowlist where feasible, adding WAF rules that reject encoded traversal sequences on API paths, and — for anyone building similar APIs — validating path components against an allowlist and canonicalising paths before verifying that they remain inside the permitted base directory.
Technical Details
CVE-2026-85706 is a path traversal flaw (CWE-22) in the GitLab repository commits API: the endpoint constructs a filesystem path from request-supplied data without properly confining the result to the repository's storage directory, and the same request path also fails to enforce authentication. Because both gates fail together, an entirely unauthenticated caller can issue a request whose path component resolves upward out of the repository tree and have the server return the contents of an arbitrary file it can read. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N records exactly this combination — network reachable, low complexity, no privileges, no user interaction, changed scope, high confidentiality and integrity impact, no availability impact — which is what drives the score to the 10.0 maximum. The integrity component reflects that the files reachable on a GitLab host, notably secrets and tokens, let an attacker pivot from reading to modifying the environment.
Frequently Asked Questions
Is CVE-2026-85706 being actively exploited?
Yes. CISA added CVE-2026-85706 to its Known Exploited Vulnerabilities catalog with a remediation due date of 14 September 2026, confirming exploitation in the wild. A public HackerOne report and GitLab work item describe the issue, so technical details are available to attackers as well as defenders.
What products are affected by CVE-2026-85706?
GitLab Community Edition and Enterprise Edition are affected in all versions from 18.7 before 19.1.8, from 19.2 before 19.2.6 and from 19.3 before 19.3.2. Self-managed instances exposing the repository commits API are the primary risk; GitLab has remediated the issue in the listed patch releases.
How do I fix CVE-2026-85706?
Upgrade GitLab CE/EE to 19.1.8, 19.2.6 or 19.3.2 or later, matching your current release line. Because the flaw allows unauthenticated arbitrary file read, also rotate the GitLab secrets file, database credentials, access tokens, runner tokens, deploy keys and CI/CD variables, and review logs for traversal attempts against the commits API.
How severe is CVE-2026-85706?
It is Critical, with the maximum CVSS 3.1 base score of 10.0. The vulnerability is unauthenticated, network-exploitable, requires no user interaction, crosses a security scope boundary and delivers high confidentiality and integrity impact through arbitrary file read on the GitLab server; combined with confirmed KEV-listed exploitation, it is a top-priority emergency patch despite an EPSS score around the 65th percentile.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.