A maximum-severity vulnerability affecting the enterprise source code management and DevOps platform GitLab has come under active, automated in-the-wild exploitation just 24 hours after public disclosure. The flaw, designated as CVE-2026-85706, was assigned a maximum possible severity score of 10.0 on the global CVSS (Common Vulnerability Scoring System, a standardized industry framework used to quantify the characteristics and severity of software vulnerabilities). Exploitation attempts were detected on September 11, 2026, by threat intelligence researchers at cybersecurity firm watchTowr, prompting the U.S. Cybersecurity and Infrastructure Security Agency (CISA) to immediately add the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog. The security flaw allows completely unauthenticated remote adversaries to exfiltrate arbitrary files, credentials, and cryptographic keys from the underlying server operating system through a single crafted HTTP request directed at GitLab's web interface.
GitLab represents one of the world's most widely adopted repository management platforms, trusted by tens of thousands of enterprises, government agencies, and financial institutions to orchestrate mission-critical software pipelines. The root flaw resides within GitLab's internal commit handling functionality exposed via its API (Application Programming Interface, a defined communication interface enabling automated interaction between software systems). Owing to an improper input neutralization defect resulting in a Path Traversal (directory traversal, a programming vulnerability where an attacker manipulates file paths using characters like ../ to navigate outside restricted folders), threat actors can inject arbitrary paths into the `file.path` parameter submitted during an HTTP POST request to the endpoint `/api/v4/projects/{id}/repository/commits/`.
Because the application fails to adequately sanitize this parameter before accessing the local filesystem, an attacker can traverse out of the project repository directory. With a single unauthenticated web request requiring no credentials, API tokens, or session cookies, an attacker can extract sensitive operational files such as `/etc/passwd`, database configuration files, SSH keys (Secure Shell, cryptographic key pairs utilized for authenticating developer access and server administration), GitLab Runner registration tokens, and environmental variables configured across automated build pipelines.
Within hours of GitLab issuing its emergency security patch on September 10, 2026, automated scanning infrastructure and opportunistic threat actors began scanning the public internet for vulnerable instances. Threat intelligence researchers at watchTowr issued an immediate warning on Friday after observing active probes:
> "watchTowr Intel is already observing in-the-wild probes for the latest critical GitLab Path Traversal vulnerability, CVE-2026-85706, which allows attackers to read arbitrary files in a single HTTP request. Organizations with public-facing self-hosted GitLab instances should patch as soon as possible or remove public access."
Cybersecurity analyst and Security Affairs founder Pierluigi Paganini emphasized the severity of the threat, drawing attention to previous historical precedents within the GitLab ecosystem:
> "GitLab has seen similar path traversal flaws exploited quickly. CVE-2023-2825, which also allowed arbitrary file reads, faced active attacks just days after disclosure. CVE-2026-85706 followed the same pattern, with attackers starting probes even faster than expected. Organizations should treat the flaw as an urgent threat, not wait for widespread exploitation to begin."
The primary danger of arbitrary file disclosure on a version control server lies in the high-privilege credentials typically hosted in configuration vaults. Should an attacker extract GitLab's master configuration secret `gitlab-secrets.json`, all encrypted database secrets and tokens become decipherable. Furthermore, extracting deploy tokens and API credentials embedded in CI/CD pipelines (Continuous Integration and Continuous Deployment, automated frameworks for software testing and delivery) grants attackers the ability to tamper with production builds, plant covert backdoors into enterprise software releases, or pivot into linked enterprise clouds on AWS, Microsoft Azure, or Google Cloud without triggering password alarms.
The vulnerability impacts all deployments of GitLab Community Edition (CE) and GitLab Enterprise Edition (EE) across the following version ranges:
- Version 18.7 and later prior to 19.1.8
- Version 19.2 prior to 19.2.6
- Version 19.3 prior to 19.3.2
In the same security advisory, GitLab resolved CVE-2026-87719, an insecure deserialization vulnerability affecting the advanced search functionality that could allow credential disclosure. Consequently, superficial web application firewall (WAF) filtering is insufficient; administrators must apply the official vendor patches to comprehensively secure their infrastructure.
Actionable Guidance for Security and DevOps Teams
Organizations and public-sector bodies hosting self-managed GitLab instances must take immediate containment and verification actions:
- Upgrade to Patched Releases Immediately: Deploy GitLab versions 19.1.8, 19.2.6, or 19.3.2 across all production servers without delay. If immediate maintenance cannot be scheduled, immediately restrict external access by isolating the GitLab instance behind an internal corporate VPN requiring multi-factor authentication.
- Audit Web Server and API Telemetry: Query GitLab application telemetry (`production_json.log` and `api_json.log`) and upstream NGINX access logs for incoming HTTP POST calls matching the URI pattern `/api/v4/projects/.*/repository/commits/` where payloads contain the `file.path` key or directory traversal indicators (`../`, `%2e%2e%2f`, or doubly-encoded traversal strings).
- Isolate Suspicious Endpoints: If incoming requests containing traversal sequences are identified, treat the host as compromised. Sever external network connections and acquire volatile RAM memory captures and forensic disk images for thorough post-incident analysis.
- Rotate All Production Secrets and Credentials: Because threat actors may have exfiltrated sensitive files prior to patching, upgrading the software is only the first step. DevOps teams must immediately rotate all SSH server keys, database passwords, GitLab Runner authentication tokens, personal access tokens (PATs), and CI/CD environment secrets across all projects.
Immediate Checklist for IT and Security Directors
1. Verify Perimeter Exposure: Scan external network perimeters using tools like Shodan or Censys to ensure self-hosted GitLab interfaces are not publicly accessible to unauthorized internet traffic. 2. Conduct Source Code Integrity Audits: Verify cryptographic hashes (SHA-256) across recent branch commits to ensure no unauthorized code modifications or commits were injected by compromised accounts. 3. Validate CI/CD Build Artifacts: Inspect recently compiled container images and deployment binaries to ensure that rogue build steps were not introduced via compromised pipeline runner environments.
Evidence Rail
- Confirmed: In-the-wild exploitation and automated scanning confirmed by watchTowr Intel, alongside formal cataloging by CISA in the Known Exploited Vulnerabilities (KEV) database.
- Reported: Vulnerability breakdown and version analysis published by Security Affairs (Pierluigi Paganini) and GitLab's official security advisory team.
- Unconfirmed: The total volume of compromised global GitLab servers and potentially exfiltrated proprietary repositories remains under active cross-border investigation.
In Brief
- A critical vulnerability in GitLab's commits API (CVE-2026-85706) with a CVSS 10.0 rating is under active exploitation just 24 hours post-disclosure.
- Unauthenticated remote actors can read arbitrary files, SSH keys, and CI/CD secrets through a single crafted HTTP POST request.
- System administrators must immediately update to versions 19.1.8, 19.2.6, or 19.3.2, audit commit API logs for traversal strings, and rotate all production credentials.