<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/maximum-severity-gitlab-flaw-puts-supply-chains-at-risk-10bpjbbfl" -->

---
title: Maximum Severity GitLab Flaw Puts Supply Chains at Risk
description: A maximum-severity path traversal vulnerability, CVE-2026-85706, in GitLab Community Edition and Enterprise Edition is being actively exploited in the wild,...
canonical: https://daily.dev/posts/maximum-severity-gitlab-flaw-puts-supply-chains-at-risk-10bpjbbfl
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Maximum Severity GitLab Flaw Puts Supply Chains at Risk | daily.dev
og:description: A maximum-severity path traversal vulnerability, CVE-2026-85706, in GitLab Community Edition and Enterprise Edition is being actively exploited in the wild,...
og:url: https://daily.dev/posts/maximum-severity-gitlab-flaw-puts-supply-chains-at-risk-10bpjbbfl
og:image: https://api.daily.dev/og/posts/10bpjbBFl.png
og:image:alt: Maximum Severity GitLab Flaw Puts Supply Chains at Risk
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Maximum Severity GitLab Flaw Puts Supply Chains at Risk

**[Dark Reading](https://daily.dev/sources/dr)** · 4 min read · 0 upvotes · 0 comments

## Summary

A maximum-severity path traversal vulnerability, CVE-2026-85706, in GitLab Community Edition and Enterprise Edition is being actively exploited in the wild, allowing unauthenticated attackers to read arbitrary files from self-hosted GitLab servers. GitLab patched the flaw on September 10 with a CVSS score of 10/10, and CISA added it to its Known Exploited Vulnerabilities catalog, requiring federal agencies to patch by a set deadline. Researchers at watchTowr observed attackers dumping config files, secrets, and SSH configurations from victim systems, potentially enabling full instance compromise and further access into organizations' development environments. Exploitation requires at least one public project on the GitLab instance. Affected organizations should update to versions 19.3.2, 19.2.6, or 19.1.8, or remove public access if patching isn't immediately possible. This follows a separate GraphQL code injection flaw (CVE-2026-19478) exploited last month.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.darkreading.com/cyberattacks-data-breaches/maximum-severity-gitlab-flaw-supply-chains-risk>

## Questions this post answers

### What is CVE-2026-85706 and which GitLab versions does it affect?

CVE-2026-85706 is a maximum-severity path traversal vulnerability with a CVSS score of 10 out of 10, affecting GitLab Community Edition and Enterprise Edition self-hosted instances. It stems from improper path confinement and missing authentication checks in the repository commits API, letting unauthenticated attackers read arbitrary files from the server. GitLab patched it on September 10 in versions 19.3.2, 19.2.6, and 19.1.8.

_Teams running self-hosted GitLab can track patch advisories like this one on daily.dev to stay ahead of exploitation._

### What can attackers actually access by exploiting the GitLab path traversal flaw CVE-2026-85706?

Attackers get read-only access to arbitrary files, but that has been enough to dump configuration files containing secrets and SSH configurations from victim systems. Combined, these let attackers extract passwords, connect to systems with password authentication enabled, and potentially gain full host access, along with CI/CD secrets that expose the broader software supply chain.

_Security teams weighing supply chain exposure from CI/CD secrets can follow coverage like this on daily.dev._

### How do I mitigate CVE-2026-85706 if I cannot immediately patch my GitLab instance?

Immediately remove all public access to the GitLab instance if you cannot update right away, since exploitation requires at least one public project on the server. GitLab Dedicated customers do not need to act, and GitLab.com has already patched the flaw. Security teams should also review access logs on the repository commits API for suspicious unauthenticated requests indicating probing or exploitation.

_Ops teams triaging urgent GitLab advisories can keep watch on follow-up guidance via daily.dev._

## Similar posts on daily.dev

- [GitLab Vulnerability Under Active Exploitation Enables Unauthenticated Data Exfiltration](https://daily.dev/posts/gitlab-vulnerability-under-active-exploitation-enables-unauthenticated-data-exfiltration-5hnex7c8x) · InfoQ · 0 upvotes · 0 comments
- [Hackers now exploit critical Gitea flaw in code injection attacks](https://daily.dev/posts/hackers-now-exploit-critical-gitea-flaw-in-code-injection-attacks-gmz4nkjzi) · BleepingComputer · 2 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#cicd](https://daily.dev/tags/cicd), [#gitlab](https://daily.dev/tags/gitlab)

[View this post on daily.dev](https://daily.dev/posts/maximum-severity-gitlab-flaw-puts-supply-chains-at-risk-10bpjbbfl)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Maximum Severity GitLab Flaw Puts Supply Chains at Risk","url":"https://daily.dev/posts/maximum-severity-gitlab-flaw-puts-supply-chains-at-risk-10bpjbbfl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/maximum-severity-gitlab-flaw-puts-supply-chains-at-risk-10bpjbbfl"},"datePublished":"2026-09-14T20:36:08.114Z","dateModified":"2026-10-15T02:22:58.652Z","description":"A maximum-severity path traversal vulnerability, CVE-2026-85706, in GitLab Community Edition and Enterprise Edition is being actively exploited in the wild,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/54f6071cb34f45b9db163ead2e55ef39?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/54f6071cb34f45b9db163ead2e55ef39?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Dark Reading","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Dark Reading","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/dr","url":"https://daily.dev/sources/dr"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/maximum-severity-gitlab-flaw-puts-supply-chains-at-risk-10bpjbbfl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,cicd,gitlab","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Dark Reading","item":"https://daily.dev/sources/dr"},{"@type":"ListItem","position":3,"name":"Maximum Severity GitLab Flaw Puts Supply Chains at Risk"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/maximum-severity-gitlab-flaw-puts-supply-chains-at-risk-10bpjbbfl#faq","mainEntity":[{"@type":"Question","name":"What is CVE-2026-85706 and which GitLab versions does it affect?","acceptedAnswer":{"@type":"Answer","text":"CVE-2026-85706 is a maximum-severity path traversal vulnerability with a CVSS score of 10 out of 10, affecting GitLab Community Edition and Enterprise Edition self-hosted instances. It stems from improper path confinement and missing authentication checks in the repository commits API, letting unauthenticated attackers read arbitrary files from the server. GitLab patched it on September 10 in versions 19.3.2, 19.2.6, and 19.1.8. Teams running self-hosted GitLab can track patch advisories like this one on daily.dev to stay ahead of exploitation."}},{"@type":"Question","name":"What can attackers actually access by exploiting the GitLab path traversal flaw CVE-2026-85706?","acceptedAnswer":{"@type":"Answer","text":"Attackers get read-only access to arbitrary files, but that has been enough to dump configuration files containing secrets and SSH configurations from victim systems. Combined, these let attackers extract passwords, connect to systems with password authentication enabled, and potentially gain full host access, along with CI/CD secrets that expose the broader software supply chain. Security teams weighing supply chain exposure from CI/CD secrets can follow coverage like this on daily.dev."}},{"@type":"Question","name":"How do I mitigate CVE-2026-85706 if I cannot immediately patch my GitLab instance?","acceptedAnswer":{"@type":"Answer","text":"Immediately remove all public access to the GitLab instance if you cannot update right away, since exploitation requires at least one public project on the server. GitLab Dedicated customers do not need to act, and GitLab.com has already patched the flaw. Security teams should also review access logs on the repository commits API for suspicious unauthenticated requests indicating probing or exploitation. Ops teams triaging urgent GitLab advisories can keep watch on follow-up guidance via daily.dev."}}]}
```

