CVE-2026-85706: GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
- Is it exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 11 Sep 2026, 1 day before the CVE record was published.
- How likely is exploitation in the next 30 days?
- 97.4%
EPSS score, percentile 99.9 of all scored records
- How severe?
- 10.0 Critical
CVSS v3.1 base score, given by the CNA
- What should I do?
Required action (CISA), due 14 Sep 2026: 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.
The CVE record links no vendor advisory, patch or mitigation.
- Which versions are affected?
Affected: 18.7 up to, not including, 18.11.12; 19.0 up to, not including, 19.0.9; 19.1 up to, not including, 19.1.8; 19.2 up to, not including, 19.2.6; 19.3 up to, not including, 19.3.2
Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of 28 Oct 2026; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of 28 Oct 2026; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.
What to do
Required action, set by CISA
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.
CISA due date for this action: 14 September 2026.
Solution (from the CVE record)
Upgrade to versions 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2 or above.
Advisories and patches
The CVE record links no vendor advisory, patch or mitigation.
Linked from CISA's catalog entry
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-85706
Affected products and versions
As listed in the CVE record.
| Status | Versions |
|---|---|
| Affected | 18.7 up to, not including, 18.11.12 |
| Affected | 19.0 up to, not including, 19.0.9 |
| Affected | 19.1 up to, not including, 19.1.8 |
| Affected | 19.2 up to, not including, 19.2.6 |
| Affected | 19.3 up to, not including, 19.3.2 |
Versions not listed are: unaffected.
Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.
About this vulnerability
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.
Summary: CISA's KEV catalog, as of 28 Oct 2026.
- CISA added CVE-2026-85706 to its Known Exploited Vulnerabilities (KEV) catalog on 11 Sep 2026.
- CISA's ransomware flag for this entry is "Unknown": no evidence of ransomware use in the catalog, which is not proof of none.
- The due date CISA sets for the required action is 14 Sep 2026.
- The CVE record was published on 12 Sep 2026, 1 day after it was added to KEV.
- The CVE record carries a CVSS v3.1 base score of 10.0 (Critical), given by its CNA.
- FIRST's EPSS model puts the probability of exploitation in the next 30 days at 97.4% (percentile 99.9), as of 28 Oct 2026.
- CISA's SSVC assessment in the CVE record: exploitation active, automatable yes, technical impact total.
Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of 28 Oct 2026; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of 28 Oct 2026. About the data.
Description
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.
Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of 28 Oct 2026. About the data.
Weakness
CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record and the KEV entry.
Timeline
| Date | Event |
|---|---|
| 11 Sep 2026 | Added to CISA KEV |
| 12 Sep 2026 | CVE record published |
| 14 Sep 2026 | CISA due date for the required action |
| 23 Sep 2026 | CVE record last updated |
References
More exploited GitLab vulnerabilities
- CVE-2021-22175: GitLab Server-Side Request Forgery (SSRF) Vulnerability
- CVE-2021-39935: GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) Vulnerability
- CVE-2023-7028: GitLab Community and Enterprise Editions Improper Access Control Vulnerability
- CVE-2021-22205: GitLab Community and Enterprise Editions Remote Code Execution Vulnerability