An unauthenticated request could read files off a GitLab server
On 10 September 2026 GitLab released versions 19.3.2, 19.2.6 and 19.1.8 of Community Edition and Enterprise Edition. One of the fixes was CVE-2026-85706, a path traversal flaw in the repository commits API. According to the vendor, under certain conditions an unauthenticated user could read arbitrary files from the GitLab server, because the endpoint neither confined the path it was handed nor enforced authentication. GitLab assigned the flaw a score of 10.0, and the vector held in NVD is the vendor's own, listed there as a secondary source. The vector says the attack can be carried out over the network, at low complexity, with no privileges required and no user interaction.
A day later CISA added the vulnerability to its Known Exploited Vulnerabilities catalog, with a due date of 14 September for US federal agencies. The entry asks for forensic triage as well as patching, and records the use in ransomware campaigns as unknown. watchTowr wrote the same day that it had reproduced the flaw and was seeing probes for it across its global honeypot network. Its advice is to hunt through logs for POST requests to the commits API that carry a file.path parameter.
The first patch covered only the three newest branches, while affected versions reach back to 18.7. The fix for 19.0.9 and 18.11.12 arrived on 23 September. GitLab.com was already running a patched version according to the vendor, and GitLab Dedicated customers need take no action. For installations that organisations run themselves the vendor also shipped three threat detections for attempts to read files through the flaw, one of them for attempts to fetch the gitlab.yml configuration file.
What this means for you if you run GitLab yourself
The question that decides your exposure is which branch your installation sits on. On 19.1, 19.2 or 19.3 you had a patched version on 10 September and can close this out with an upgrade. On 18.7 to 18.11 or on 19.0, no patched version below 19.1.8 existed until 23 September, when GitLab backported the fix to 19.0.9 and 18.11.12. The KEV due date fell on 14 September, nine days before the fix reached the older branches. From 10 September the fix sat only further up, which meant a jump out of your own branch. Our assessment is that a gap like that cannot be covered by patching routines alone. What works in the meantime is taking the server off the open internet or putting a gate in front of it, and somebody has to make that call while the gap stays open.
Then there is the question of whether something has already happened. CISA asked for forensic triage and not only for patching, and that advice holds for you even when no US directive binds you. A flaw granting read access without authentication leaves little behind beyond lines in a log, and the files it could reach may be the ones that hold the secrets of your build chain. If you cannot rule out that somebody fetched gitlab.yml or its equivalent, it is the keys that need replacing, not just the version number.
Berigo recommends
- Find every GitLab installation your organisation runs itself, and write down the exact version number of each one.
- Upgrade to 19.3.2, 19.2.6, 19.1.8, 19.0.9 or 18.11.12, depending on the branch the installation sits on.
- Take GitLab off the open internet wherever the service does not need to be reachable from there, and put authentication or a VPN in front of the rest.
- Review the commits API logs from the period before you upgraded, and deploy the three detections GitLab published.
- Rotate the secrets that sat readable on the server, meaning configuration keys and build chain variables, if you cannot rule out that they were read.
Security that is understood, governed and works.
Let us help you turn security into an advantage, not a cost. Get in touch for a no-obligation conversation about where your organisation stands and what to prioritise first.
Get in touch