CVE-2026-85706: GitLab Community Edition and Enterprise Edition Path Traversal
GitLab Community Edition and Enterprise Edition · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-11.
- CVSS v3.1 (CVE record)
- 10.0
- critical
- EPSS (exploit probability, 30 days)
- 97%
- higher than 99.8% of all CVEs
- Added to CISA KEV
- 2026-09-11
- US federal due date 2026-09-14
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2026-85706 explained
CVE-2026-85706 is a critical path traversal vulnerability in GitLab Community Edition and Enterprise Edition. Improper path confinement and missing authentication enforcement in the repository commits API could let an unauthenticated user read arbitrary files from the GitLab server. CISA lists it as known to be exploited.
Impact
A remote, unauthenticated attacker could read arbitrary files from the GitLab server under certain conditions, with no user interaction. The CVSS vector shows network access, low complexity, changed scope and high confidentiality and integrity impact. CISA rates it automatable, so it can be exploited at scale, with total technical impact. Attackers are known to use this vulnerability; ransomware use is unknown.
Who is affected
GitLab CE/EE is affected in these ranges: ≥ 18.7, < 18.11.12, ≥ 19.0, < 19.0.9, ≥ 19.1, < 19.1.8, ≥ 19.2, < 19.2.6 and ≥ 19.3, < 19.3.2. Fixed versions are 18.11.12, 19.0.9, 19.1.8, 19.2.6 and 19.3.2. Upgrade to the fixed version matching your release line.
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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 notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- GitLabAffectedFixed in
- ≥ 18.7, < 18.11.12
- ≥ 19.0, < 19.0.9
- ≥ 19.1, < 19.1.8
- ≥ 19.2, < 19.2.6
- ≥ 19.3, < 19.3.2
- 18.11.12
- 19.0.9
- 19.1.8
- 19.2.6
- 19.3.2
| Product | Affected | Fixed in |
|---|---|---|
| GitLab |
|
|
How to fix it
- Update to a fixed version: 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2.
- Vendor advisory: docs.gitlab.com/releases/patches/patch-release-gitlab-19-…
- CISA's deadline for US federal agencies: 2026-09-14 (passed) – a useful benchmark for everyone else, too.
What to do
- Upgrade GitLab CE/EE to
18.11.12,19.0.9,19.1.8,19.2.6or19.3.2, matching your release line. - Treat this as urgent: CISA lists it as known exploited, with a US federal due date of 2026-09-14.
- Follow the GitLab vendor advisory and apply any mitigations it describes if you cannot upgrade immediately.
- Restrict network exposure of GitLab instances, especially from the internet, until patched.
- Check servers for signs of compromise, including unexpected file access through the API, and rotate secrets stored on the server if exposure is suspected.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Questions about CVE-2026-85706
- Does an attacker need an account to exploit CVE-2026-85706?
- No. The description states an unauthenticated user could read arbitrary files under certain conditions, and the CVSS vector requires no privileges and no user interaction.
- Is this vulnerability exploited in the wild?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-09-11. Whether it is used in ransomware campaigns is unknown.
- Which version should I install?
- Install the fixed release for your line:
18.11.12,19.0.9,19.1.8,19.2.6or19.3.2. Versions from18.7onward below these fixes are affected.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.