CVE-2026-85706

CriticalActively exploited (CISA KEV)

Description

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.

SeverityCritical
CVSS10.0
Exploit probability—
ProductGitLab Community Edition and Enterprise Edition
PublishedSep 12, 2026
First seenSep 12, 2026
Added to KEVSep 11, 2026

How to fix

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.

CISA due date: Sep 14, 2026
Update
  • gitlab gitlab18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2 or later

Affected products

ProductAffected versionsFixed in
gitlab gitlab18.7.0 ≤ v < 18.11.12, 19.0.0 ≤ v < 19.0.9, 19.1.0 ≤ v < 19.1.8, 19.2.0 ≤ v < 19.2.6, 19.3.0 ≤ v < 19.3.218.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.