GitLab Patches Critical Path Traversal Flaw After Probing Begins

· Original article ↗

Summary

GitLab patched CVE-2026-85706, a maximum-severity path traversal flaw that could expose arbitrary data under certain conditions. watchTowr reported probing of exposed, unpatched servers; GitLab also fixed CVE-2026-87719.

Key points

  • CVE-2026-85706 stems from improper path confinement and missing authentication enforcement in the repository commits API; attackers could read arbitrary data under certain conditions.
  • watchTowr reported in-the-wild probing for exposed GitLab servers vulnerable to CVE-2026-85706; GitLab had not flagged the flaw as exploited in the wild.
  • Defenders were advised to check logs for POST requests to the repository commits API containing a file.path parameter.
  • GitLab also fixed CVE-2026-87719, an insecure deserialization flaw affecting GitLab EE that could let authenticated users with Duo Chat access steal sensitive credentials and Advanced Search configurations.
  • Fixed versions include GitLab CE and EE 19.3.2, 19.2.6, and 19.1; GitLab urged self-managed customers to upgrade immediately.
  • GitLab.com was already patched, and GitLab Dedicated customers were told no action was needed.

Article Details

Vulnerability Types
  • Path traversal
  • Insecure deserialization
Severity
Maximum severity for CVE-2026-85706; critical for CVE-2026-87719
Exploitation Status
reported
Exploit Availability
unknown
Patch Status
available

MITRE ATT&CK

CVE

People

Vendors

Products

Related Articles