GitLab Path Traversal Exploitation Attempts Observed One Day After Disclosure

· Original article ↗

Summary

WatchTowr reports in-the-wild probes targeting GitLab CVE-2026-85706 one day after disclosure. The unauthenticated path traversal can expose arbitrary server files; affected self-hosted instances should upgrade to patched releases.

Key points

  • WatchTowr said it observed exploitation attempts one day after GitLab disclosed patches for CVE-2026-85706.
  • The critical path traversal flaw can let unauthenticated users read arbitrary files from a GitLab server.
  • Affected versions are CE/EE releases before 19.1.8, 19.2.6, and 19.3.2, within the specified release branches.
  • WatchTowr advised defenders to check logs for HTTP POST requests to `/api/v4/projects/{id}/repository/commits/` containing `file.path` parameters.
  • GitLab's patched releases also fix 17 other vulnerabilities, including CVE-2026-87719, a critical GraphQL subscription serializer issue.
  • The same releases address high-severity flaws that could enable remote code execution, access to protected CI/CD variables, XSS, or denial of service.

Article Details

Vulnerability Types
  • Path traversal
  • Insecure deserialization
Severity
CVE-2026-85706: CVSS 10/10; CVE-2026-87719: CVSS 9.9/10
Affected Versions
  • GitLab Community Edition and Enterprise Edition: versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2
Exploitation Status
active
Exploit Availability
unknown
Patch Status
available
Workarounds
  • Hunt log files for HTTP POST requests to /api/v4/projects/{id}/repository/commits/ URIs containing file.path parameters to identify potential exploitation attempts.

CVE

People

Vendors

Related Articles