"Based on recent GitLab vulnerabilities, we know the time until indiscriminate exploitation is likely not far away," said cybersecurity vendor watchtower after detecting active probes for a critical GitLab bug.
CVE-2026-85706: a path traversal that can expose arbitrary files
The flaw, tracked as CVE-2026-85706, is described in technical terms as an "improper limitation of a pathname to a restricted directory" — commonly called a path traversal vulnerability. According to a GitLab security advisory, the bug affected GitLab CE/EE instances "from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2" and, "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."
GitLab remediation and timeline
GitLab fixed the issue on September 10. The vendor's advisory explicitly states that it "has remediated an issue in GitLab CE/EE" across the listed versions and described the repository commits API as the locus of the missing authentication enforcement and path confinement error. The advisory places the vulnerability squarely in the mechanism that accepts commit data, and the remediation targets the affected CE/EE versions named above.
This site is the portfolio.
OSINTSights runs on Cloudflare Workers, D1, R2, and Vectorize, with an AI pipeline on Hetzner ARM. Nubivance designed, built, and operates it. We do the same for clients.
See what we buildWatchtower detection and practical indicators
While GitLab itself had not flagged evidence of exploitation at the time of its advisory, external observers reported otherwise. On September 11, watchtower said it had detected "in-the-wild probes" for CVE-2026-85706 and urged rapid action. The vendor recommended that "organizations with public-facing self-hosted GitLab instances should patch as soon as possible or remove public access."
Watchtower also published a concrete hunt technique for defenders: search log files for HTTP POST requests to "/api/v4/projects/{{id}}/repository/commits/" that contain "file.path" parameters. That pattern targets the repository commits API endpoint that the advisory identified and provides a focused indicator for teams triaging potential attempts.
CISA adds CVE-2026-85706 to the KEV Catalog and sets a federal deadline
On the same day GitLab issued its fix, the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-85706 to its Known Exploited Vulnerabilities (KEV) Catalog. In its notice, CISA warned that "this type of vulnerability is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise."
CISA's KEV listing carries a compliance implication for the civilian federal enterprise: only civilian federal agencies are mandated to fix vulnerabilities on the KEV list, and for this bug the federal remediation deadline is September 15. CISA additionally advised agencies and organizations to "follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable."
How technologists, civilian agencies, and self‑hosted enterprises are likely to respond
- Technologists and security teams — Patch or firewall public access. Security teams with public-facing, self-hosted GitLab instances will be expected to apply the GitLab updates for the affected versions immediately; where patches cannot be deployed quickly, watchtower explicitly advised removing public access and hunting logs for the specified POST requests that include "file.path" parameters.
- Civilian federal agencies — Meet the September 15 KEV deadline. Civilian agencies face a short, defined remediation window under the KEV requirement and will need to either apply the fixes, follow applicable BOD 26-04 guidance for cloud services, or discontinue use of affected products if mitigations are not available.
- Enterprises running self‑hosted GitLab — Prioritize inventory and exposure. Organizations that operate their own GitLab instances must confirm whether they run affected versions (18.7 through early 19.3 releases listed in the advisory), close any public-facing exposure, and hunt for the commit-API POST indicators watchtower outlined.
What the presence of active probes and AI-enabled threat research means now
The incident combines three concrete elements: a high-severity path traversal (CVE-2026-85706), an official remediation on September 10, and detections of in-the-wild probing reported on September 11. Security observers tied faster weaponization cycles to the growing use of AI by would-be attackers; the reporting notes that security experts have warned AI tools are helping adversaries "weaponize new vulnerabilities much quicker than before" and find novel flaws more easily. The article also cites Google Threat Intelligence Group (GTIG) from May, which claimed a first in revealing threat actors using AI to identify and exploit a zero-day.
With CISA's KEV listing and a federal deadline of September 15 closing the window for mandated fixes, the practical consequence is immediate: organizations running public-facing, self-hosted GitLab instances must either patch the affected versions, remove public access, or follow the cloud-guidance route CISA provides. Watchtower's log-hunt recipe gives defenders a narrow, actionable detection path; whether it will catch probing before data is read remains the urgent operational question.
