CVE of the month: GitLab CVE-2026-85706, reading server files without login
September 2026. A vulnerability rated CVSS 10 on the server that holds all of a company's source code was in the catalog of exploited vulnerabilities one day after the patch. What happened, who is affected and what to do if you run your own GitLab.
Sources: NVD · GitLab bulletins of 10 September and 23 September 2026 · CISA KEV
Checklist
- GitLab version is 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2 or newer
- GitLab is not directly reachable from the internet
- Logs checked for commits API requests with suspicious paths since 10 September
- If there are signs of compromise, tokens, keys and CI/CD variables have been replaced
- GitLab stays on a supported branch
What happened
The GitLab repository commits API checked neither the file path nor the user's login. Anyone who could reach the GitLab server could read an arbitrary file from that server without logging in. The CVSS score is 10.0 out of 10: a network attack, with no account and no action by the victim.
- Vulnerability class: path traversal (CWE-22); vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N.
- 10 September 2026: GitLab released fixes in versions 19.3.2, 19.2.6 and 19.1.8.
- 11 September: CISA added the vulnerability to the Known Exploited Vulnerabilities (KEV) catalog; the deadline for US federal agencies was 14 September.
- In CISA's assessment: exploitation is active, the attack can be automated, the impact is total.
CVE recordGitLab has remediated an issue in GitLab CE/EE … 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.editors' translation
Who is affected
Only self-managed GitLab installations, both Community and Enterprise Edition. GitLab.com and GitLab Dedicated were fixed by GitLab.
- Vulnerable versions: 18.7 up to 18.11.12, 19.0 up to 19.0.9, 19.1 up to 19.1.8, 19.2 up to 19.2.6 and 19.3 up to 19.3.2.
- Safe versions: 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2 and newer.
- The most dangerous case is a GitLab reachable from the internet. An internal server is also at risk: an attacker inside the network does not need a login either.
Why this matters more than an ordinary CVE
GitLab is not just another server. It holds all of the company's source code, the CI/CD configuration and the credentials pipelines use to reach other systems. The ability to read files from such a server is a direct path to a supply chain attack: the code and configuration show how the other systems are built.
- Among the detection rules GitLab published for its customers is an attempt to read gitlab.yml, the configuration of the server itself.
- For banks this is the system where, under ARDFM Resolution No. 53 (clause 147), source code is also kept inside the perimeter.
- At the same time GitLab fixed a second critical vulnerability, CVE-2026-87719 in Enterprise Edition (insecure deserialization in GraphQL; it needs an account with access to Duo Chat).
Lesson of the month: 13 days without a fix on older branches
The fixes of 10 September were released only for the three newest branches. For 18.11 and 19.0 GitLab released separate versions on 23 September, outside its usual support policy. Anyone on an older branch lived for 13 days with an exploited vulnerability and no patch, or had to upgrade urgently across several major versions.
- Keep GitLab on supported branches: the further behind you are, the more steps there are to the fix on the day of an attack.
- Do not expose GitLab to the internet directly; use a VPN or an allowlist of addresses. That is the compensating measure for the days when there is no patch.
- Follow the catalog of exploited vulnerabilities: one day passed between the patch and KEV.
What to do if you run your own GitLab
Steps are in order of urgency.
- Check the version (in the interface, the Help page or the admin area) and update to the safe version of your branch.
- If GitLab is reachable from the internet, close outside access until you have updated.
- Check web server logs for commits API requests with suspicious paths since 10 September. GitLab published three detection rules for this vulnerability.
- If there are signs that files were read, treat the secrets stored on the server as compromised: tokens, keys, CI/CD variables. Replace them.
- Check the other development systems on the same principle: Jenkins, Nexus, Artifactory, SonarQube are also part of the supply chain.
Questions and answers
Is GitLab.com affected?
No. According to the GitLab bulletin, GitLab.com already runs a fixed version, and GitLab Dedicated customers do not need to do anything. Only self-managed installations are vulnerable.
Which GitLab versions are safe?
18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2 and newer. Versions before 18.7 are not affected by this vulnerability, but they are outside GitLab's support policy and receive no other security fixes.
Does the attacker need an account?
No. The vulnerability is exploited without authentication, over the network, with no user action, which is why the CVSS score is 10.0.
Is the vulnerability being exploited?
Yes. On 11 September 2026 CISA added CVE-2026-85706 to the Known Exploited Vulnerabilities (KEV) catalog.
Review based on open sources as of 11 October 2026. Current versions and details are in the GitLab bulletins.