GitLab CE/EE Repository Commits API Path Traversal Vulnerability

Technical Analysis

The vulnerability stems from improper path confinement combined with missing authentication enforcement in the repository commits API endpoint, allowing unauthenticated requests to traverse the filesystem outside the intended repository directory using crafted path sequences (e.g., '../' style traversal). Successful exploitation permits attackers to read arbitrary files on the underlying host, potentially exposing configuration files, SSH keys, database credentials, GitLab secrets_yml, CI/CD variables, and .env files without requiring any prior authentication. Because CISA has added this to the KEV catalog, active in-the-wild exploitation is confirmed, and organizations should treat this as an imminent threat rather than theoretical risk. GitLab instances are widely used as the backbone for CI/CD pipelines that build, test, and deploy AI agent frameworks and RAG pipelines, meaning exposed CI/CD secrets, API keys (including LLM provider keys such as OpenAI/Anthropic tokens), and pipeline configuration files stored in or accessible via these repositories could be exfiltrated, enabling downstream compromise of agent credentials, model endpoints, and automated deployment pipelines.

Affected Systems

GitLab Community Edition (CE) and Enterprise Edition (EE) instances exposing the repository commits API; specific vulnerable version ranges should be confirmed against GitLab's official security advisory, but all self-managed and potentially GitLab.com-adjacent deployments running affected releases are at risk, particularly those with internet-facing GitLab instances.

Indicators of Compromise

• Anomalous requests to /api/v4/projects/:id/repository/commits endpoints containing path traversal sequences (../, ..%2F, %252e%252e%252f)
• Unexpected 200 OK responses returning file contents outside repository scope
• Requests to sensitive file paths such as /etc/passwd, config/secrets.yml, .env, config/database.yml via the commits API
• Unauthenticated access log entries to repository/commits endpoints from unusual source IPs
• Spikes in GitLab access/audit logs for the affected API path without corresponding valid session tokens

Remediation Steps

1. 1

   Apply GitLab Security Patch Immediately

   Upgrade GitLab CE/EE to the patched version specified in GitLab's official security release addressing CVE-2026-85706 without delay, prioritizing internet-facing instances.

2. 2

   Restrict External Access to GitLab API

   Temporarily restrict or firewall access to the repository commits API endpoint from untrusted networks until patching is complete.

3. 3

   Audit Access Logs

   Review GitLab access and audit logs for anomalous unauthenticated requests to the repository/commits API, especially those containing path traversal patterns, dating back to before the KEV addition date.

4. 4

   Rotate Exposed Secrets

   Rotate all credentials, API keys (including any LLM/AI service provider keys), SSH keys, and CI/CD variables that may have been stored in or accessible through the GitLab instance, assuming potential compromise.

5. 5

   Enable WAF/Path Traversal Protections

   Deploy or update Web Application Firewall rules to detect and block path traversal patterns targeting GitLab API endpoints as a compensating control.

6. 6

   Monitor for Post-Exploitation Activity

   Monitor for subsequent unauthorized access using any credentials or secrets that may have been exposed through file disclosure, including agent/API tooling that consumes GitLab-stored secrets.