How severe is CVE-2026-85706?

No CVSS score has been assigned to CVE-2026-85706 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-85706?

CVE-2026-85706 affects the following packages: gitlab (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2026-85706?

Update gitlab to 18.11.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-85706 is resolved across your whole dependency graph.

How do I detect CVE-2026-85706 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gitlab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-85706 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-85706 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2026-85706, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2026-85706?

CVE-2026-85706 has an EPSS (Exploit Prediction Scoring System) score of 93.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2026-85706 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-85706 (GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-09-11. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-09-14. The required action was: 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. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-85706?

CVE-2026-85706 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2026-85706?

A Nuclei detection template exists for CVE-2026-85706, meaning automated scanners can fingerprint it. 2 Metasploit modules reference CVE-2026-85706, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-85706 published, and has it been updated?

CVE-2026-85706 was published on September 15, 2026 and was last updated on September 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

CISA KEV · ACTIVELY EXPLOITED

CVE-2026-85706 — gitlab

CVE-2026-85706 is a Path Traversal vulnerability in gitlab. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-09-11) — treat it as actively exploited and patch now. A fix is available for gitlab — see the affected versions and patch details below.

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

Published

Sep 15, 2026

Updated

Sep 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

5 known

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-09-11. Federal agencies were required to remediate by 2026-09-14.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-85706.

EPSS Exploitation Probability

via FIRST.org ↗

93.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦gitlab

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`gitlab`	≥ 18.7.0&&< 18.11.12	18.11.12

Affected Products

1 product · 10 configurations

Application

gitlabgitlab

≥ 19.3.0 && < 19.3.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

guneykabel/cve-2026-85706

Exploit poc for CVE-2026-85706 an unauthenticated arbitrary file read on

⭐ 44🍴 4Sep 2026

EQSTLab/CVE-2026-85706

GitLab Unauthenticated Arbitrary File Read

⭐ 25🍴 4Sep 2026

mhtsec/CVE-2026-85706

GitLab CE/EE unauthenticated path traversal (CVE-2026-85706) - PoC

⭐ 12🍴 3Sep 2026

ynsmroztas/GitLabSniper

CVE-2026-85706 Unauthenticated File Read

⭐ 8🍴 2Sep 2026

0xlyvio/cve-2026-85706-poc-exploit-gitlab

cve-2026-85706-poc-exploit-gitlab

⭐ 4🍴 0Sep 2026

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gitlab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gitlab to 18.11.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-85706 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How to detect CVE-2026-85706

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2026-85706 -u https://target

Template: GitLab CE/EE <=19.1.7/19.2.5/19.3.1 - Arbitrary File Read
Severity: critical
Impact: Unauthenticated remote attackers can read any file accessible to the GitLab git user, including /etc/passwd, database credentials, secrets.yml, SSH private keys, and CI build artifacts, which in turn enables session forgery and full compromise of the instance. Exploitation requires at least one publicly readable project on the target.
Remediation: Upgrade GitLab CE/EE to 19.1.8, 19.2.6, or 19.3.2 or later. The fix moves authenticate! ahead of file processing and stops accepting raw file.path and file.size parameters from untrusted clients.

Template by ProjectDiscovery nuclei-templates (FLX), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-85706 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works