CVE-2026-85706

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab

CRITICAL
10
CVSS Score
Published: September 12, 2026 at 02:46 AM UTC
Updated: September 24, 2026 at 01:07 PM UTC
1 product affected across 1 vendorGitLab

Using GitLab by GitLab?

Get instant alerts when new vulnerabilities affect GitLab - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL10
Exploitation
CISA KEV
Exploit prediction
EPSS 97%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score97.4%

EPSS (Exploit Prediction Scoring System) estimates a 97.4% chance this CVE is exploited in the wild within the next 30 days — higher than 100% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

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.

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.
Ransomware Use
Unknown
Added to KEV
Sep 11, 2026
Remediation Due
Sep 14, 2026
48 days overdue

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

18.7 ≤ v < 18.11.1218.7.0 ≤ v < 18.11.1219.0 ≤ v < 19.0.919.0.0 ≤ v < 19.0.919.1 ≤ v < 19.1.819.1.0 ≤ v < 19.1.819.2 ≤ v < 19.2.619.2.0 ≤ v < 19.2.619.3 ≤ v < 19.3.219.3.0 ≤ v < 19.3.218.719.019.119.219.3
Affected range stops below 18.11.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.0.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.2.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (3)

Technical DescriptionExploitPermissions Required
Source: cverecord
https://hackerone.com/reports/3909881
Third Party AdvisoryUS Government Resource
Source: 134c704f-9b21-4f2e-91b3-4a467353bcc0
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-85706

SSVC — Action Prioritization

SSVCActiveAutomatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

10CRITICALGitLab
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-22

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card