Vulnerability · CVE-2026-85706
GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
Published Sep 11, 2026 · catalog updated Sep 24, 2026 · GitLab Community Edition and Enterprise Edition
Patch now
CVE-2026-85706 is in the CISA known-exploited catalog, due Sep 14, 2026. Confirm GitLab Community Edition and Enterprise Edition against the vendor advisory and apply that fix. The CVSS score does not change the priority.
Gaps on this record
- No version range is stored. A customer cannot check an installed version against this record.
- Severity
- Critical10.0
- Known exploitation
- CISA KEV and VulnCheck KEV
- EPSS
- 92.96%
- Remediation
- Remediation guidance
- Affected products
- cpe gitlab/gitlab · vendor GitLab Community Edition and Enterprise Edition
Overview On September 10, 2026, GitLab published a critical patch release for GitLab Community Edition (CE) and Enterprise Edition (EE). The release addresses CVE-2026-85706 , a critical path traversal vulnerability ( CWE-22 ) in the repository commits API with a CVSSv3.1 score of 10.0 . According to GitLab, improper path confinement and missing authentication enforcement could allow an unauthenticated user to read arbitrary files from an affected GitLab server under certain conditions. On September 11, 2026, CVE-2026-85706 was added to the U.S. Cybersecurity and Infrastructure Security Agency
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe gitlab/gitlabversion unspecified
- vendor GitLab Community Edition and Enterprise Editionversion unspecified
How to fix CVE-2026-85706
Recommended remediation
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 due date Sep 14, 2026.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2026-85706 is in the CISA known-exploited catalog, due Sep 14, 2026. Confirm GitLab Community Edition and Enterprise Edition against the vendor advisory and apply that fix. The CVSS score does not change the priority.
Which versions are affected?
Affected version ranges are not on this record. 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.
What should an analyst verify?
CWE-22: Path Traversal; CWE-35. EPSS 92.96%. The CISA KEV listing is the exploitation evidence. A public exploit reference is linked in Sources. That is not the same as confirmed exploitation. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 11, 2026 · Catalog
Detected
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.
Sep 11, 2026 · CISA KEV
Known exploited
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
Sep 14, 2026 · CISA KEV
Remediation due
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
Sep 24, 2026 · Catalog
Updated
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.
Sources
- CISA KEVConfirmed exploitationCVE-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.
cisa.gov - CVE.orgVulnerability recordCVE-2026-85706
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-85706
30-day exploitation probability 93.0%
first.org - GitLab Security ReleasesVendor advisoryCVE-2026-85706
On September 23, 2026, we released versions 19.0.9 and 18.11.12 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions backport the fixes for two critical vulnerabilities, CVE-2026-85706 and CVE-2026-87719, that were originally patched in 19.3.2, 19.2.6, an
docs.gitlab.com - Metasploit ModulesPublic exploit moduleauxiliary_gather/gitlab_file_read_cve_2026_85706
Public module reference (normal). Module source is not copied into this catalog.
rapid7.com - Nuclei TemplatesDetection templateCVE-2026-85706
CVE-2026-85706 has a public Nuclei detection template.
github.com - NIST NVDVulnerability recordCVE-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 Git
nvd.nist.gov - Rapid7 Vulnerability DatabaseResearchCVE-2026-85706
Overview On September 10, 2026, GitLab published a critical patch release for GitLab Community Edition (CE) and Enterprise Edition (EE). The release addresses CVE-2026-85706 , a critical path traversal vulnerability ( CWE-22 ) in the repository commits API with a CVSSv3.1 score of 10.0 . According to GitLab, improper path confinement and missing authentication enforcement could allow an unauthenti
rapid7.com - VulnCheck KEVConfirmed exploitationCVE-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.
vulncheck.com
References
- VulnCheck exploitation evidence · api.vulncheck.com
- VulnCheck exploitation evidence · api.vulncheck.com
- VulnCheck exploitation evidence · api.vulncheck.com
- CISA note · docs.gitlab.com
- VulnCheck exploitation evidence · fortiguard.fortinet.com
- Broken Link · gitlab.com
- Permissions Required · hackerone.com
- CISA note · nvd.nist.gov
- Third Party Advisory · cisa.gov
- CISA note · cisa.gov
- CISA note · cisa.gov
- VulnCheck exploitation evidence · cisa.gov
- VulnCheck exploitation evidence · x.com
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.