Hackers Exploit Maximum Severity Flaw in GitLab
Vulnerability: GitLab users must patch CVE-2026-85706, a critical path traversal flaw actively exploited to read arbitrary files.
Deep Analysis and Expert Commentary
The vulnerability exploits improper path confinement in GitLab's repository commits API, enabling unauthenticated attackers to bypass directory restrictions and access sensitive files. Affected versions include GitLab CE/EE 18.7 to 19.3.2, with exploitation already observed in the wild. Attackers likely probe for vulnerable instances via HTTP POST requests to specific URIs containing 'file.path' parameters. Mitigations include immediate patching to versions 19.1.8, 19.2.6, or 19.3.2, or restricting public access to self-hosted instances. Log monitoring for suspicious API requests is critical for early detection. The rapid inclusion in CISA's KEV catalog underscores the high risk of widespread exploitation.
Action Items
- Patch GitLab instances to versions 19.1.8, 19.2.6, or 19.3.2 immediately.
- Monitor logs for HTTP POST requests to '/api/v4/projects/{id}/repository/commits/' with 'file.path' parameters.
- Restrict public access to self-hosted GitLab instances if patching is delayed.
Original Article Brief Intro
Infosecurity Magazine · 2026-09-14 · Vulnerability: GitLab users must patch CVE-2026-85706, a critical path traversal flaw actively exploited to read arbitrary files.
Related Terms and Notes
CVE IDs
- CVE-2026-85706 — A critical path traversal flaw in GitLab allowing unauthenticated file reads.
Context Notes
- CISA KEV
- GitLab
- GitLab vulnerability
- Path traversal — A vulnerability enabling access to files outside restricted directories.