CVE-2026-85706: critical vulnerability in GitLab
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
Patch now. It under exploitation confirmed by CISA, has an official Brazilian government alert and has a working public exploit.
Brazil's federal government published an alert, recommendation or bulletin that cites this vulnerability.
- CISC Gov.br · 14 Oct 2026Boletim do CISC de Vulnerabilidadesread on gov.br ↗
- CISC Gov.br · 16 Sep 2026Boletim do CISC de Vulnerabilidadesread on gov.br ↗
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.
An unauthenticated attacker can read any file from a GitLab server by exploiting a path traversal flaw in the repository commits API. This is critical because it allows unauthorized access to sensitive data without needing to log in.
A path traversal vulnerability in GitLab's repository commits API permits unauthenticated users to bypass path confinement controls and read arbitrary files from the server filesystem. The flaw stems from improper input validation and missing authentication enforcement; attackers can craft malicious API requests to traverse directory restrictions and access sensitive data.
In the same product, most dangerous first.