Critical GitLab File-Read Flaw CVE-2026-85706 Exploited; Patch Self-Managed Instances

· Original article ↗

Summary

CVE-2026-85706 lets unauthenticated attackers read files from vulnerable self-managed GitLab servers. CISA confirmed exploitation; GitLab has patched affected releases, and exposed instances should be investigated and credentials rotated.

Key points

  • The flaw affects self-managed GitLab Community and Enterprise editions and allows unauthenticated file reads through repository APIs; a real public project is required.
  • Affected versions are fixed in GitLab 19.1.8, 19.2.6, and 19.3.2. GitLab.com and GitLab Dedicated were updated by the vendor.
  • CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on September 11, 2026, after confirming exploitation; public reporting said probing began within a day of the patch release.
  • The article advises restricting network access if an upgrade is delayed and treating internet-facing instances left unpatched after September 10 as potentially compromised.
  • Investigators can search GitLab’s api_json.log and web-tier logs for suspicious file.path or metadata.path parameters; a 2xx response from the same anonymous caller may indicate a confirmed read.
  • After a confirmed read, investigate the exposure window and rotate at-risk credentials, while checking for unexpected tokens, pipeline runs, runner registrations, SSH access, and cloud or registry logins.

Article Details

Vulnerability Types
  • Unauthenticated arbitrary file read
  • Path traversal
Severity
Critical; CVSS 10.0
Affected Versions
  • GitLab Community Edition 18.7 through 19.1.7
  • GitLab Enterprise Edition 18.7 through 19.1.7
  • GitLab Community Edition 19.2.0 through 19.2.5
  • GitLab Enterprise Edition 19.2.0 through 19.2.5
  • GitLab Community Edition 19.3.0 through 19.3.1
  • GitLab Enterprise Edition 19.3.0 through 19.3.1
Exploitation Status
active
Exploit Availability
public_exploit
Patch Status
available
Workarounds
  • Restrict network access to the instance by removing it from the public internet or limiting access to trusted address ranges.
  • Review public project visibility; exploitation requires a public project to provide a usable project ID.

MITRE ATT&CK

CVE

Vendors

Products

Tools

Related Articles