CVEs / CVE-2026-85706
CVE-2026-85706: GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
- Known exploited in the CISA KEV catalog since 11 Sep 2026
- critical 10 CVSS 3.1 (from the CNA)
- EPSS 97.3% chance of exploitation in the next 30 days, higher than 99% of CVEs (30 Oct 2026)
- Last changed at its sources
Are you affected? Check your servers with Stackurity: it lists the software on each server and the vulnerabilities to fix first.
Check your servers with Stackurity Already using Stackurity? Search for CVE-2026-85706
Summary
GitLab Community Edition and Enterprise Edition contains a path traversal vulnerability that allows an unauthenticated user to read arbitrary files due to an improper path confinement and missing authentication enforcement in the repository commits API.
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.
Affected and fixed versions
| Product | Affected | Fixed in |
|---|---|---|
| GitLab GitLab | from 18.7, before 18.11.12 | 18.11.12 |
| GitLab GitLab | from 19.0, before 19.0.9 | 19.0.9 |
| GitLab GitLab | from 19.1, before 19.1.8 | 19.1.8 |
| GitLab GitLab | from 19.2, before 19.2.6 | 19.2.6 |
| GitLab GitLab | from 19.3, before 19.3.2 | 19.3.2 |
Exploitation
| In CISA KEV since | 11 Sep 2026 |
|---|---|
| Due date for US federal agencies | 14 Sep 2026 |
| Used in ransomware campaigns | Unknown |
| Required action | Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. |
Severity
| CVSS 3.1 | 10 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NScored by the CNA ([email protected]) |
|---|---|
| Weakness | CWE-22 |
References
- CVE-2026-85706 on NVD
- CVE-2026-85706 in the CISA KEV catalog
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/ (cited by CISA)
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (cited by CISA)
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk (cited by CISA)
- CVE-2026-85706 on OSV
- 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
Sources
Exploitation status from the CISA Known Exploited Vulnerabilities catalog. EPSS scores from FIRST. Descriptions, severity and references from the National Vulnerability Database. Open-source package versions from OSV (CC-BY 4.0). Text is shown as each source states it; Stackurity does not edit it. Check the vendor's advisory before acting.
This product uses data from the NVD API but is not endorsed or certified by the NVD.