VULNpocalypse

CVE-2026-85706: GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by GitLab, published 2026-09-12).

Weakness: CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.

On CISA KEV since
2026-09-11
US federal deadline
2026-09-14
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-14538, EUVD-2026-76779, GHSA-f47w-mrg9-g9p2, SNYK-MINIMOSLATEST-GITLABRUNNERHELPEROCIENTRYPOINT193-19829921

VEDAS cluster: VEDAS:DRAGONMOUNT

Exploit Observer links 24 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (24)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (5)

Vulnerability databases and vendor advisories (6)

Catalogue entries, not exploit evidence.

News (2)

118 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.974
very likely to be attacked soon
VEDAS
0.986
strong exploit evidence
On CISA KEV
Yes, since 2026-09-11
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
100.1CVE-2026-85706 EPSS over time2026-092026-11-01
VEDAS (exploit evidence)
100.9CVE-2026-85706 VEDAS over time2026-092026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
GitLab GitLabfrom 18.7 before 18.11.12
from 19.0 before 19.0.9
from 19.1 before 19.1.8
from 19.2 before 19.2.6
from 19.3 before 19.3.2		Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: gitlab gitlab, gitlab_inc. gitlab.

How to fix it

Fixed versions stated in the CVE record: 18.11.12, 19.0.9, 19.1.8, 19.2.6, 19.3.2.

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.

Vendor guidance:

How to detect it

Nuclei template (active check)

GitLab CE/EE Affecting All Versions - Path Traversal

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.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (POST /api/v4/projects/1/repository/%66iles/{{randstr}}?file=&file.path=/...); it decides using status, word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-85706.yaml
Show the template (40 lines)
yaml
id: CVE-2026-85706

info:
  name: "GitLab CE/EE Affecting All Versions - Path Traversal"
  author: vedas-arpsyndicate
  severity: critical
  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.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-85706&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=gitlab&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
    cvss-score: 10.0
    cve-id: CVE-2026-85706
    cwe-id: CWE-22
  metadata:
    verified: false
  tags: cve,cve2026,gitlab,lfi,unauth,kev,vkev,vuln
http:
  - raw:
      - |
        POST /api/v4/projects/1/repository/%66iles/{{randstr}}?file=&file.path=/cve-2026-85706-ulaxki-probe&file.size=1&Content-Type=application/x-www-form-urlencoded HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded
        Accept: application/json, */*

    matchers-condition: and
    matchers:
      - type: word
        part: body
        words:
          - "local file not present"

      - type: status
        status:
          - 400

CVE-2026-85706.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-85706 GitLab CE/EE Affecting All Versions - Path Traversal. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-85706 GitLab CE/EE Affecting All Versions - Path Traversal"; flow:established,to_server; http.uri; content:"repository"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-85706; reference:url,https://www.exploit.observer/?keyword=CVE-2026-85706&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=gitlab&match=exact; sid:1010200; rev:1;)

CVE-2026-85706.rules on GitHub

References

Exploits and technical analysis

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.