CVE-2026-85706
CriticalExploitedPublic exploitGitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLa
Published Sep 12, 2026 · Updated Sep 24, 2026 · Also known as BIT-gitlab-2026-85706, EUVD-2026-76779, GHSA-f47w-mrg9-g9p2
Key Facts
Patch immediately- CVE-2026-85706 is a critical-severity vulnerability (CVSS 10.0 v3.1) affecting GitLab, gitlab-pages-19.1 (chainguard), gitlab-rails-ce-18.11 (chainguard) and 22 more products.
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Sep 11, 2026. Public exploit code is available.
- EPSS estimates a 93% probability of exploitation in the next 30 days.
- Fixed versions are available, including GitLab 19.1.8, GitLab 19.2.6, GitLab 19.3.2.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
EPSS (30-day exploit likelihood)
93%
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2026-85706 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Sep 11, 2026 | Sep 14, 2026 | Not reported |
| Industry KEV feed | Sep 11, 2026 | Sep 14, 2026 | Not reported |
| CIRCL KEV | Sep 11, 2026 | Sep 14, 2026 | Not reported |
| ENISA EUVD | Sep 11, 2026 | n/a | Not reported |
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Affected Products
34 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| GitLabGitlab | >= 18.7.0, >= 19.3 | 19.1.8 |
| gitlab-pages-19.1chainguard | See advisory | 19.1.8-r0 |
| gitlab-rails-ce-18.11chainguard | See advisory | 18.11.12-r0 |
| gitlab-rails-ce-19.0chainguard | See advisory | 19.0.9-r0 |
| gitlab-rails-ce-fips-18.11chainguard | See advisory | 18.11.12-r0 |
Patched Releases
GitLab
19.1.8, 19.2.6, 19.3.2, 18.11.12, 19.0.9
gitlab-cng-19.0
19.0.9-r0
gitlab-cng-19.1
19.1.8-r0
gitlab-cng-19.2
19.2.6-r0
gitlab-cng-19.3
19.3.2-r0
gitlab-cng-fips-18.11
18.11.12-r0
gitlab-cng-fips-19.0
19.0.9-r0
gitlab-cng-fips-19.1
19.1.8-r0
gitlab-cng-fips-19.2
19.2.6-r0
gitlab-cng-fips-19.3
19.3.2-r0
gitlab-pages-19.1
19.1.8-r0
gitlab-rails-19.1
19.1.8-r0
gitlab-rails-19.2
19.2.6-r0
gitlab-rails-19.3
19.3.2-r0
gitlab-rails-ce-18.11
18.11.12-r0
gitlab-rails-ce-19.0
19.0.9-r0
gitlab-rails-ce-fips-18.11
18.11.12-r0
gitlab-rails-ce-fips-19.0
19.0.9-r0
gitlab-runner-19.2
19.2.6-r0
gitlab-runner-19.3
19.3.2-r0
gitlab-runner-fips-19.2
19.2.6-r0
gitlab-runner-fips-19.3
19.3.2-r0
gitlab-workhorse-ce-18.11
18.11.12-r0
gitlab-workhorse-ce-19.0
19.0.9-r0
gitlab-workhorse-ce-fips-18.11
18.11.12-r0
Timeline
Added to CISA KEV
Sep 11, 2026
Added to Industry KEV feed
Sep 11, 2026
Added to CIRCL KEV
Sep 11, 2026
Added to ENISA EUVD
Sep 11, 2026
Publicly disclosed
Sep 12, 2026
Last updated
Sep 24, 2026
Weakness Type
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
References
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
- articlehttps://nvd.nist.gov/vuln/detail/CVE-2026-85706
FAQ
Common Questions.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confine…
Affected: GitLab versions >= 18.7.0, >= 19.3; gitlab-pages-19.1 (chainguard); gitlab-rails-ce-18.11 (chainguard), among others. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Sep 11, 2026.
Yes. It was added on Sep 11, 2026 with a federal remediation due date of Sep 14, 2026.
Public exploit code is available.
Fixed versions are available, including GitLab 19.1.8, GitLab 19.2.6, GitLab 19.3.2.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2026-85706 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo