Skip to content
Fencer Vulns
critical 10.0

CVE-2026-85706 kev in the critical feed json

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab

published 2026-09-12 58 d ago modified 2026-09-25 44 d ago also BIT-gitlab-2026-85706 , EUVD-2026-76779

cvss
10.0
version 3.1, CNA
cisa kev
Exploited
added 2026-09-11
epss
97.4%
EPSS 97.4% chance of exploitation in 30 days, percentile 99.8%
public exploits
1
Metasploit, plus a Nuclei check

Summary

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.

Patch / fix

cisa 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.

  • bitnami gitlab 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2
  • GitLab GitLab 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2

Timeline

  1. First public exploit (Metasploit auxiliary/gather/gitlab_file_read_cve_2026_85706)
  2. Added to CISA KEV
  3. Published
  4. CISA SSVC: exploitation active
  5. CISA patch deadline

Known exploited

Added
59 d ago
Patch by
2026-09-14 (56 d ago)
Ransomware
Not known
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.
Vendor, product
GitLab, Community Edition and Enterprise Edition
CISA name
GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
57 d ago

Exploit prediction

97.36% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
OSV 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=18.7.0, <18.11.12
>=19.0.0, <19.0.9
>=19.1.0, <19.1.8
>=19.2.0, <19.2.6
>=19.3.0, <19.3.2
18.11.12
19.0.9
19.1.8
19.2.6
19.3.2

Affected products

  • GitLab GitLab

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.