· via dev.to (home feed)
GitLab patches CVSS-10 unauthenticated file read in commits API as CISA confirms active exploitation
GitLab has fixed a CVSS 10.0 unauthenticated path traversal in the repository commits API, and CISA's exploitation catalog confirms attackers are already using it against unpatched self-managed instances.
GitLab has fixed a maximum-severity path traversal flaw in its repository commits API that let an unauthenticated attacker read arbitrary files from the server, and CISA has added the vulnerability to its catalog of actively exploited flaws.
The bug is tracked as CVE-2026-85706. According to a Netics write-up published on dev.to, GitLab shipped the fix in a critical patch release on September 11, 2026 — versions 19.3.2, 19.2.6 and 19.1.8, one per supported release line — and CISA added the CVE to its Known Exploited Vulnerabilities (KEV) catalog the same day, a listing the agency reserves for vulnerabilities with evidence of real-world attacks.
Two missing checks, maximum severity
The GitLab advisory, as relayed by dev.to, attributes the flaw to path confinement that was not properly enforced combined with authentication checks that were missing on the commits API endpoint. In other words, the endpoint failed at two basic jobs at once: keeping requested file paths inside their intended root, and verifying who was making the request.
The resulting CVSS score is 10.0, the top of the scale, with a vector indicating the flaw is network-reachable and requires no privileges and no user interaction. On a self-managed instance, the files an attacker could reach include gitlab.yml and the secrets it holds, repository contents, OAuth tokens and anything else readable by the Rails process, according to the dev.to analysis. A file-read primitive in the system that stores a company's source code is about as damaging as primitives get.
The KEV listing is the priority signal
CISA only adds vulnerabilities to KEV when it has evidence of active exploitation, and under directive BOD 26-04 the entry sets rapid-remediation deadlines for US federal agencies. For everyone else, the dev.to author notes, the listing is the clearest public indicator that attackers are already using the flaw — which turns the usual upgrade-planning debate into a straightforward "patch now".
A wide affected range
GitLab's advisory lists three affected ranges: GitLab CE/EE from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2, with each release line having its own fixed version. The dev.to post argues that the bigger practical risk sits just outside those ranges: instances parked on older majors such as 18.x or 17.x, often in containers or VMs untouched for months. The advisory's impact statement starts at 18.7, but because the commits API exists in every GitLab, the author's recommendation is that older instances assume exposure as well and plan a full upgrade.
The exposure is uneven in one important way. Per GitLab's notes, the hosted services GitLab.com and GitLab Dedicated are already patched. Self-managed instances have to apply the fix themselves.
What admins should do
The order of operations recommended in the dev.to post is patch first, before anything else. Upgrade to 19.3.2, 19.2.6 or 19.1.8 or later depending on your release line, then confirm the running version. Only then comes the retrospective. GitLab published three threat detections for self-managed instances — one catching a file-inclusion attempt that reads gitlab.yml, one catching traversal through a metadata path parameter, and one catching file-path enumeration. Apply them, then replay them against historical access logs. The post warns that this is the hard part: the malicious requests look like ordinary commits-API calls and would not stand out in a routine log review. Any secrets that may have been readable should be rotated.
Why it matters
This is the rare vulnerability where severity and real-world evidence align: a perfect CVSS score on an internet-reachable, unauthenticated file read in the platform that holds an organisation's source code, secrets and CI configuration, with CISA confirming attacks in the wild. It also sharpens the self-managed-versus-hosted trade-off — the control of running your own GitLab comes with the obligation to move it within days of a KEV entry. And it is a reminder that detection, not patching, is often the weaker link: without the specific signatures, exploitation of this flaw would be indistinguishable from normal API traffic.
- #gitlab
- #security
- #cve
- #path-traversal
- #patch-management
- #cisa