GitLab Community Edition and Enterprise Edition
CVE-2026-85706
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.
What this means for your business
- It affects GitLab Community Edition and Enterprise Edition. It matters if your company, or a supplier that handles your data, runs it.
- Attackers are already using it. CISA added it to its list of flaws used in real attacks on 11 September 2026.
- An attacker can use it remotely, over a network, without a login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 12% chance of attack attempts being seen in the next 30 days, ranking above 95% of all known flaws.
What to do
- 1Check whether your company or your suppliers run GitLab Community Edition and Enterprise Edition, and which version. The affected versions are listed further down this page.
- 2If you do, follow CISA's required action below. No patch reference has been published yet.
- 3Treat it as urgent. US federal agencies must fix it by 14 September 2026. That deadline does not apply to private companies, but it shows how seriously CISA takes it.
- 4Because attackers have used it, check the affected systems for signs of a break-in, not only for the update.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
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.
CISA’s wording, unedited. The notes it mentions are in CISA’s catalogue entry.
Scoring
- CVSS
- 10.0 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N- Weakness
- CWE-22
- Assigned by
- cve@gitlab.com
Dates
- Published
- 2026-09-11
- Last modified
- 2026-09-14
- Added to KEV
- 2026-09-11
- Remediation due
- 2026-09-14
- Sources
- CISA KEV, NVD
Affected products
- Gitlab Gitlab18.7.0 - 19.1.8, 19.2.0 - 19.2.6, 19.3.0 - 19.3.2
As listed in the NVD configuration data. Not a statement about your estate.
Coverage
- Maximum Severity GitLab Flaw Puts Supply Chains at RiskDark Reading · 2026-09-14
- CVE-2026-85706: Critical GitLab Path Traversal Exploited in the WildRapid7 Blog · 2026-09-14