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.
Critical 10.0Actively exploited
CVE-2026-85706
GitLab Community Edition and Enterprise Edition — Path Traversal.
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…
WeaknessCWE-22: Path traversal
Published Updated Source NVD and CISA KEV
CVSS 3.1
10.0
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Exploit chance, 30 days
97%
Higher than 99% of all CVEs (EPSS)
Status
Actively exploited
On CISA KEV since 11 Sep 2026
Patch
Unknown
Check the vendor advisory
What happened
What to do
- 01Check whether you run GitLab Community Edition and Enterprise Edition, and which version.
- 02Follow the vendor advisory for a fix or a workaround.
- 03Apply 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 deadlineUS federal agencies must remediate by
References
Timeline · UTC
- Added to CISA KEV
- Published to NVD
- CISA remediation deadline
- NVD record updated
Also actively exploited
Other CVEs from GitLab
3 more CVEs, 1 actively exploited