Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-85706 – Unauthenticated Arbitrary File Read – GitLab CE/EE 18.7–19.3.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-85706 is a critical path traversal vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE) that allows an unauthenticated attacker to read arbitrary files from the underlying GitLab server. The flaw resides in the repository commits API, where improper path confinement and missing authentication enforcement let API requests escape the intended repository scope and reach files on the host filesystem. GitLab rated the issue CVSS 10.0 (Critical) and it has been added to CISA’s Known Exploited Vulnerabilities catalog following reports of active internet-wide probing shortly after patches were released.

Technical details

  • Root cause: improper limitation of a pathname to a restricted directory (path traversal, CWE-22) combined with missing authentication enforcement in the repository commits API endpoint.
  • Trigger condition: an attacker sends a crafted request (reported to involve the /api/v4/projects/{id}/repository/commits/ endpoint with a manipulated file path parameter) that is not confined to the intended repository directory.
  • Attack vector: network, no authentication or user interaction required, low attack complexity.
  • Impact: unauthenticated disclosure of arbitrary files readable by the GitLab service account on the affected server; no reported impact to integrity or availability from this specific flaw.
  • The issue was reported to GitLab via its HackerOne bug bounty program by a researcher using the handle "s3ntago."
  • GitLab.com and GitLab Dedicated were already running patched code at the time of disclosure and required no customer action; the risk applies to self-managed instances.

Affected software

  • GitLab CE/EE 18.7 through 19.1.7
  • GitLab CE/EE 19.2.0 through 19.2.5
  • GitLab CE/EE 19.3.0 through 19.3.1

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: upgrade self-managed GitLab instances to version 19.1.8, 19.2.6, 19.3.2, or later, as released by GitLab.
  • If immediate patching is not possible: restrict network access to the GitLab instance (e.g., limit exposure of the API/web interface to trusted networks or VPN) to reduce the attack surface until the upgrade can be applied; no other functional workaround has been published.
  • Review server and application logs for anomalous requests to the repository commits API that reference file path parameters outside expected repository paths, as this endpoint has been reported as the target of post-disclosure scanning activity.
  • Confirm GitLab.com or GitLab Dedicated usage is unaffected, as these hosted offerings were already remediated prior to public disclosure.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge