← Back to CVE intelligence
CVE intelligenceCISA KEV

CVE-2026-85706

GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability

Published Sep 12, 2026Sources checked Nov 20, 2026
10.0CRITICALCVSS out of 10
What this means

Actively exploited

CISA lists CVE-2026-85706 in its Known Exploited Vulnerabilities catalog, which means exploitation has been observed. The entry applies to GitLab Community Edition and Enterprise Edition.

  • 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 KEVListedObserved exploitation
EPSS97.4%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors1Source-linked actor relationships
Publisher research

Version guidance and technical research

Collected from the publisher for this CVE. Check the source for configuration requirements and supported upgrade paths.

GitLab

Vendor-listed versions for CVE-2026-85706. A fixed release does not establish the state of your systems.
ProductAffected versionsFixed release
GitLab CE/EE18.7 up to, but not including, 18.11.1218.11.12
GitLab CE/EE19.0 up to, but not including, 19.0.919.0.9
GitLab CE/EE19.1 up to, but not including, 19.1.819.1.8
GitLab CE/EE19.2 up to, but not including, 19.2.619.2.6
GitLab CE/EE19.3 up to, but not including, 19.3.219.3.2

Follow the vendor upgrade path and check deployment-specific prerequisites.

Read GitLab: GitLab Critical Patch Release: 19.0.9, 18.11.12

Published 2026-09-23. Last successful check: 2026-11-20 04:00 UTC.

GitLab

Vendor-listed versions for CVE-2026-85706. A fixed release does not establish the state of your systems.
ProductAffected versionsFixed release
GitLab CE/EE18.7 up to, but not including, 18.11.1218.11.12
GitLab CE/EE19.0 up to, but not including, 19.0.919.0.9
GitLab CE/EE19.1 up to, but not including, 19.1.819.1.8
GitLab CE/EE19.2 up to, but not including, 19.2.619.2.6
GitLab CE/EE19.3 up to, but not including, 19.3.219.3.2

Follow the vendor upgrade path and check deployment-specific prerequisites.

Read GitLab: GitLab Critical Patch Release: 19.3.2, 19.2.6, 19.1.8

Published 2026-09-10. Last successful check: 2026-11-19 23:35 UTC.

Overview

What is CVE-2026-85706?

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: NVD

CISA says: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 catalog due date Sep 14, 2026