GitLab · GitLab · CWE-35 · published 2026-09-12
CVE-2026-85706GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
Patch today Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
CVE-2026-85706 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-09-11. EPSS estimates a 97.4% chance of exploitation in the next 30 days, higher than 99% of all CVEs. This GitLab vulnerability: CVSS 10.0 (v3.1), attacks can be automated, a successful attack gives total control of the component. Fixed upstream in GitLab 19.4.1, 19.3.3, 19.2.7, 19.0.9 (+4 more). US federal agencies must remediate by 2026-09-14. Patch today.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in GitLab 19.4.1, 19.3.3, 19.2.7, 19.0.9, 18.11.12, 19.3.2, 19.2.6, 19.1.8.
CISA 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. (federal due date 2026-09-14)
Patch events
DevOpsGitLab
GitLab security releases: 19.4.1, 19.3.3, 19.2.7, 19.0.9, 18.11.12
Upgrade to
19.4.119.3.319.2.719.0.918.11.12Why: CVE-2026-85706: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
DevOpsGitLab
Path TraversalCVE-2026-85706
Why: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
DevOpsGitLab
GitLab security releases: 19.3.2, 19.2.6, 19.1.8
Upgrade to
19.3.219.2.619.1.8Why: CVE-2026-85706: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2026-09-11 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 97% (100th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 10.0 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-35: Path Traversal: '.../...//'
More from this vendor: all GitLab vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- GitLab GitLab
18.7to before18.11.12(affected)19.0to before19.0.9(affected)19.1to before19.1.8(affected)19.2to before19.2.6(affected)19.3to before19.3.2(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.