CVE-2026-85706: CVSS 10 GitLab CE/EE API Flaw Actively Exploited

CVE-2026-85706 (CVSS 10, EPSS 96th pctl), published on September 12th, 2026, is a critical path traversal flaw in the GitLab CE/EE repository Commits API and Repository Files API. Exploitation can allow an unauthenticated attacker to read arbitrary files from the GitLab server on affected self-managed instances. However, the unauthenticated exploit path requires at least one anonymously readable project with repository access enabled.

The flaw was added to CISA’s Known Exploited Vulnerabilities (KEV) catalog on September 11th. Security firm watchTowr reported probes against its honeypot network. Several detailed technical analyses for CVE-2026-85706 are available, which also provide proof-of-concept (PoC) exploit code [1][2][3][4][5], further increasing the risk of ongoing attacks. Numerous national CERT alerts have been issued for CVE-2026-85706 [6][7][8][9][10][11][12][13][14][15][16][17][18].

CVE-2026-85706 was patched in a single coordinated release alongside 17 other CVEs, with one other rated critical severity. Updates for self-managed GitLab installations are available in versions 19.1.8, 19.2.6, and 19.3.2, and defenders should apply the updates as soon as possible.

A Risk Assessment of CVE-2026-85706 in GitLab CE/EE

GitLab is a widely deployed DevOps platform used for source code management, CI/CD pipelines, and application security workflows. CVE-2026-85706 is considered actively exploited and has been added to CISA’s KEV list. Several detailed technical analyses with PoC exploit code are available [1][2][3][4][5].

Instances often hold sensitive resources such as source code, credentials, and CI/CD configuration data. A remotely exploitable, unauthenticated file-read vulnerability represents critically high risk to development and software release operations. A breach may also enable supply-chain attacks, unauthorized access to cloud resources, or lateral movement within the victim’s network.

Examples include configuration and secret files such as gitlab.yml, secrets.yml, gitlab-secrets.json, and database.yml. Other potential exposures include SSH private keys, .pem certificate files, .env files, SMTP, or LDAP credentials and more. If the instance secret key base is disclosed, attackers may be able to forge sessions and tokens and decrypt stored CI/CD variables and multi-factor authentication (MFA) responses. Source code and other valuable intellectual property represent other potential data-theft risks.

Technical Details for CVE-2026-85706 in GitLab CE/EE

CVSS 10 · CriticalEPSS 11.1% (96th)Actively exploitedIn CISA KEVPublic PoC

CVE-2026-85706 (CVSS 10, EPSS ≥ 96th pctl) is a path traversal flaw [CWE-22] combined with missing authentication [CWE-306] enforcement. GitLab’s patch notes say the flaw affects the repository Commits API. However, independent analyses have also demonstrated the same vulnerable behavior in the Repository Files API, via POST and PUT operations [1].

Exploitation allows arbitrary file reads from the GitLab server rather than direct remote code execution (RCE). Exploitation also requires at least one anonymously readable project with repository access enabled. The arbitrary-file-read primitive executes with the permissions of the GitLab service context, generally the git user.

Exploitation Path and Potential Follow-On Impact

1. Exploitation can leverage a single unauthenticated POST request. Multiple working PoCs target the Content-Type: application/x-www-form-urlencoded HTTP header.
2. The malicious request must bypass the project’s authorize_read_code! check. Therefore, the attacker must identify an anonymously readable project whose repository is accessible, normally a public project.
3. Out of scope files are specified via specially crafted values for the metadata.path or file.path. Exploits can leverage route and parameter encoding techniques such as trailing-slash and percent-encoding.
4. A vulnerable GitLab server reads the attacker-selected file and returns the contents via an error-handling path that reflects the file data in an HTTP 400 response body.
5. Theft of credentials can support broader compromise, potentially leading to lateral movement within the victim’s network.

CVE-2026-85706: Affected Versions and Mitigation

CVE-2026-85706 was patched in a single release alongside 17 other CVEs, with one other rated as Critical severity. See GitLab’s release notes for affected versions of each CVE. GitLab said GitLab-managed infrastructure, including GitLab.com and GitLab Dedicated, has already been patched.

For the actively exploited CVE-2026-85706, affected versions are: 18.7 prior to 19.1.8, 19.2 prior to 19.2.6, and 19.3 prior to 19.3.2. There is no patch for 18.x or 19.0.x releases; users must move to at least 19.1.8. No workaround mitigations have been proposed by GitLab. However, reasonable temporary mitigations include removing GitLab from public Internet exposure, restricting connectivity to only trusted IP addresses, and using a web-application firewall (WAF) to specifically filter traffic targeting the Commits API and Repository Files API.

Given its actively exploited status and the operational risk of a GitLab breach, users running affected self-managed versions should accelerate patching and validation.

Product	Affected versions	Fixed versions
Self-managed GitLab CE/EE installations	18.7 before 19.1.8	19.1.8
	19.2 before 19.2.6	19.2.6
	19.3 before 19.3.2	19.3.2

Summary

CVE-2026-85706, published on September 12th, 2026, is a critical GitLab CE/EE path traversal flaw allowing unauthenticated attackers to read arbitrary files from affected self-managed servers. Exploitation represents a high degree of risk to software-producing organizations and downstream supply chains. Risk is elevated by the flaw’s actively exploited status, numerous public technical analyses, and PoC exploit code.