GitLab unauth file read, exploited (CVE-2026-85706) [PoC]

Actively exploited in the wild - CVE-2026-85706 is a critical unauthenticated arbitrary file read in GitLab CE/EE versions 18.7 through 19.1.7, 19.2.0 through 19.2.5, and 19.3.0 through 19.3.1, allowing any network attacker to read files from the GitLab server without credentials. Patched versions are 19.1.8, 19.2.6, and 19.3.2 - upgrade immediately.

Overview

CVE-2026-85706 is rated CRITICAL with a CVSS score of 10.0 (AV:N/AC:L/PR:N/UI:N), the maximum severity. The flaw combines improper path confinement with missing authentication enforcement in the repository commits API. In practice, an attacker sends crafted requests to that API endpoint and receives file contents from the underlying server filesystem. No account, token, or user interaction is required.

GitLab self-managed instances are the primary concern. GitLab.com (SaaS) runs patched code, but every on-premises deployment in the affected ranges is exposed the moment it is reachable from the internet or from any untrusted network segment.

Impact

Arbitrary file read on a GitLab server is a serious escalation primitive, not just an information leak. Attackers can target configuration files that hold database credentials, SMTP and object storage secrets, CI/CD runner tokens, and private signing keys such as gitlab-secrets.json. Those secrets frequently unlock lateral movement into integrated systems: PostgreSQL, Redis, S3 buckets, and any environment the CI runners can reach.

Because the affected endpoint requires no authentication, internet-exposed GitLab instances can be scanned and exploited at scale. Security teams should treat any unpatched instance as potentially compromised, not merely vulnerable.

Remediation

• Upgrade to GitLab 19.1.8, 19.2.6, or 19.3.2. These are the fixed releases for each maintained branch.
• If immediate upgrade is impossible, restrict network access to the GitLab web interface and API using a firewall, VPN, or reverse proxy allowlist. This is a temporary control only.
• Rotate exposed secrets after patching: database passwords, runner registration tokens, gitlab-secrets.json contents, and any credentials readable from the filesystem.
• Review GitLab access logs for requests to the repository commits API from unauthenticated or unexpected sources, and forward relevant findings to incident response.

Security Insight

CVE-2026-85706 fits a pattern that has defined GitLab’s recent security record: API endpoints that quietly skip an authorization check rather than a memory-safety bug in a parser. The CVSS 10.0 rating is earned by the combination of no authentication and no complexity, meaning scanning tooling can find and exploit victims faster than defenders can inventory their fleet. The fact that this reached active exploitation before disclosure shows that attackers are watching GitLab’s release notes closely. Organizations running self-managed GitLab should assume their upgrade cadence is now a known attack surface. For follow-on reporting, see breach reports and security news.

Further Reading

• All Critical Vulnerabilities
• Recent Critical Vulnerabilities
• Top Critical CVEs