GitLab Path Traversal Vulnerability: CVE-2026-85706 Confirmed
- Severity
- HIGH
- Affected component
- gitlab (other)
- Patched version
- Not yet available
GitLab Community Edition and Enterprise Edition contain a path traversal vulnerability that allows unauthenticated users to read arbitrary files. This vulnerability has been confirmed exploited in the wild.
What happened
The vulnerability, tracked as CVE-2026-85706, is due to improper path confinement and missing authentication enforcement in the repository commits API. An unauthenticated user can exploit this to read arbitrary files on the server.
The vulnerability was first flagged on September 11, 2026, and confirmed later the same day. Multiple independent sources have confirmed the exploit in the wild. The National Cyber Security Centre (NCSC) and CISA have published advisories on this vulnerability.
Users of GitLab Community Edition and Enterprise Edition are advised to upgrade to the latest version that patches this vulnerability. No authoritative version range has been published yet, so it is recommended to upgrade to the most recent version available.
What to do about it
- Upgrade to the latest version of GitLab Community Edition and Enterprise Edition.
- Monitor the primary sources for updates on the vulnerability and any official fixes.
- If you are using a version of GitLab prior to the patch, consider restricting access to the repository commits API until you can upgrade.
- Review your GitLab instance for any signs of unauthorized access or file reads.
- Implement additional monitoring and logging to detect any future attempts to exploit this vulnerability.
How 0Day would have caught this
gitlab is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
If you are using GitLab Community Edition or Enterprise Edition, you may be affected. No authoritative version range has been published yet, so it is recommended to upgrade to the most recent version available.
What should I do right now?
Upgrade to the latest version of GitLab Community Edition and Enterprise Edition. Monitor the primary sources for updates on the vulnerability and any official fixes.
Has this been exploited in the wild?
Yes, this vulnerability has been confirmed exploited in the wild.
Sources
- Rate limits on GitLab.com are changing
- NCSC-2026-0367 [1.00] [H/H] Kwetsbaarheid verholpen in GitLab Community en Enterprise Editions
- [GHSA-2h44-8472-frjj] @zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery
- [GHSA-cv3r-c5h8-f4g5] @zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover
- [GHSA-vmp7-252j-cwp7] @zereight/mcp-gitlab: DNS rebinding reaches local Streamable HTTP MCP transport
- [GHSA-2h44-8472-frjj] @zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery
- GitLab CVSS 10 File-Read Flaw Draws In-the-Wild Probes After Disclosure
- CISA: Hackers now exploit max severity GitLab flaw in attacks