GitLab has fixed a vulnerability in its self managed product that lets someone with no account read arbitrary files from the server, and attackers did not wait long. The patch came out on Thursday. By Friday morning researchers were already recording probes for the flaw on the internet, and the same day the US government added it to its list of vulnerabilities known to be exploited.
The bug is tracked as CVE-2026-85706 and carries the maximum severity score of 10.0. It sits in the part of GitLab's API that handles repository commits. According to GitLab, the code failed to confine file paths properly and did not enforce authentication, so that under certain conditions an unauthenticated user could read files anywhere on the GitLab server.
Why file reads are enough
Reading files sounds less alarming than running code. On a GitLab server the distinction is thin. The machine holds configuration files, logs, tokens and keys, and the secrets that build pipelines use to deploy software. An intruder who can read those can usually come back with valid credentials, and from there the source code, the pipelines and everything built by them are exposed.
The security firm watchTowr said on Friday that its sensors were seeing probes for the flaw in the wild, and that the bug can be triggered with a single HTTP request. It expects indiscriminate exploitation to follow quickly, as it has with other recent GitLab bugs. CISA appears to agree. It placed the flaw in its Known Exploited Vulnerabilities catalog on September 11 and gave federal civilian agencies until September 14 to deal with it.
Who needs to act
Customers on the hosted service do not need to do anything. GitLab says the public site was already running the patched code and that GitLab Dedicated customers are covered as well. The problem is every instance that an organization runs itself, whichever way it was installed.
The fixed releases for both the Community and Enterprise editions are:
- 19.3.2 for installations on the 19.3 line
- 19.2.6 for installations on the 19.2 line
- 19.1.8 for everything from 18.7 up to the 19.1 line
The upgrades include database migrations, so a server that runs on a single node will be unavailable while they complete. That is a poor reason to delay. The same release fixes 17 other vulnerabilities, among them CVE-2026-87719, rated 9.9, which affects the Enterprise edition and lets a logged in user with access to Duo Chat obtain sensitive credentials through a crafted GraphQL request.
Patching should not be the last step. For a flaw that was being probed within a day of the fix, administrators have to assume that an exposed server may have been read before it was updated. The advice from watchTowr is to search the logs for POST requests to /api/v4/projects/{id}/repository/commits/ that carry a file.path parameter. If such requests turn up from unknown addresses, every secret stored on or reachable from that server should be rotated.
This is not the first maximum rated path traversal flaw GitLab has had to patch. It fixed another with the same rating in May 2023, and a year later CISA and the FBI publicly urged software makers to stamp out this whole class of flaw before shipping their products.
