CVE-2026-85706
GitLab had a critical flaw that let unauthenticated users read any file on the server. The issue was fixed in certain versions. Users should upgrade to the patched releases.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
GitLab Community Edition (CE) and Enterprise Edition (EE) versions 18.7 through 19.3.1 (specifically 18.7-19.1.7, 19.2-19.2.5, and 19.3-19.3.1).
Real-world impact
An attacker could read any file on the GitLab server, potentially exposing sensitive data, credentials, or configuration files.
Why this severity
The CVSS score of 10 reflects that the vulnerability is exploitable over the network without authentication, allows complete confidentiality compromise, and has no impact on integrity or availability, making it a critical risk.
What to do about it
- 01Identify your GitLab version.
- 02Upgrade to the latest patched release (19.1.8 or later, 19.2.6 or later, or 19.3.2 or later).
- 03Restart GitLab services.
NVD-referenced vendor advisory
Timeline
- Sep 11, 2026 · 3d agoConfirmed exploited (CISA KEV)CISA added it to the Known Exploited Vulnerabilities catalog — attackers are using it in the wild.
- Sep 12, 2026 · 2d agoPublishedDisclosed and added to the National Vulnerability Database.
- Sep 12, 2026 · 1d agoOfficial fix availableA vendor patch or mitigation now exists — see the remediation steps above.
- Sep 14, 2026 · upcomingCISA remediation deadlineFederal agencies are required to remediate by this date.