Skip to navigation

Threat reportVulnerabilityTL-2026-2442

GitLab Patches Max-Severity Unauthenticated Path Traversal Flaw in Repository Commits API (CVE-2026-85706, CVSS 10.0)

criticalACTIVE

GitLab's September 10, 2026 critical patch release (19.3.2, 19.2.6, 19.1.8) fixes CVE-2026-85706, a maximum-severity (CVSS 10.0) unauthenticated path-traversal flaw in the repository commits API that lets remote attackers read arbitrary files from self-managed GitLab CE/EE servers, and CVE-2026-87719 (CVSS 9.9), an insecure-deserialization bug in the GraphQL subscription serializer that lets an authenticated user with Duo Chat access steal Advanced Search instance configuration and credentials.

Key facts

IdentifiersTL-2026-2442, CVE-2026-85706, CVE-2026-87719, CVE-2026-88765
SeverityCRITICAL
CVSS10 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N)
Exploitation statusLinked CVE exploited in the wild; Listed in CISA KEV: CVE-2026-85706 (added )
EPSSCVE-2026-85706: 1.1% (64.9th percentile); CVE-2026-88765: 0.6% (50.7th percentile); CVE-2026-87719: 0.6% (47.4th percentile)
Affected productsGitLab Inc. GitLab Community Edition (CE); GitLab Inc. GitLab Enterprise Edition (EE)
Weaknesses (CWE)CWE-22, CWE-306, CWE-502, CWE-209, CWE-35
ToolsGitLab Advanced Search, GitLab Duo Chat
MITRE ATT&CK techniquesT1005 Data from Local System, T1041 Exfiltration Over C2 Channel, T1078 Valid Accounts, T1136 Create Account, T1190 Exploit Public-Facing Application, T1211 Exploitation for Defense Evasion, T1213 Data from Information Repositories, T1213.003 Data from Information Repositories: Code Repositories, T1528 Steal Application Access Token, T1552 Unsecured Credentials, T1552.001 Unsecured Credentials: Credentials In Files, T1552.004 Unsecured Credentials: Private Keys and 7 more in the attack flow
MotivationUNKNOWN
Target sectorstechnology, software-development
Detection rules9 (1 shown free)
Sources9 cited sources

Detection coverage

As of 2026-09-14, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2442 across Splunk SPL, Microsoft KQL and Sigma, covering 48 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: GitLab Repository Commits API Path Traversal — Exploitation (CVE-2026-85706) [SPL]

Detects unauthenticated HTTP requests to the GitLab repository commits API (/api/v4/projects/:id/repository/commits) that contain path-traversal sequences (raw, URL-encoded, or double-encoded), consistent with exploitation of CVE-2026-85706 (CVSS 10.0, CWE-22/CWE-306) which allows arbitrary file read on self-managed GitLab CE/EE 18.7-19.1.7, 19.2.0-19.2.5, and 19.3.0-19.3.1. Flags requests lacking any authentication header and separately flags requests targeting known-sensitive filesystem paths (SSH keys, secrets.yml, database.yml, gitlab.rb, /etc/passwd).

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1190, T1552.001, T1552.004
  • Data sources: gitlab_production_log, nginx_access_log, gitlab_workhorse_log
  • Severity: critical
  • Confidence: high

Splunk SPL

index=gitlab (sourcetype="nginx:access" OR sourcetype="gitlab:workhorse" OR sourcetype="gitlab:production")
| eval decoded_uri=urldecode(uri)
| eval has_auth=if(match(_raw,"(?i)(Authorization:\s*Bearer|PRIVATE-TOKEN:|JOB-TOKEN:)"),1,0)
| where has_auth=0 AND match(decoded_uri,"(?i)/api/v[34]/projects/[^/\s]+/repository/commits") AND match(decoded_uri,"(\.\.\/|\.\.%2f|%2e%2e\/|%252e%252e)")
| eval sensitive_target=if(match(decoded_uri,"(?i)(id_rsa|\.ssh\/|secrets\.yml|database\.yml|gitlab\.rb|\.env|\/etc\/passwd|\/etc\/shadow|config\/secrets)"),"true","false")
| stats count as request_count min(_time) as first_seen max(_time) as last_seen values(decoded_uri) as target_paths values(sensitive_target) as sensitive_flags by src_ip, status
| where request_count>=1
| sort -request_count

Microsoft KQL

let SensitivePattern = @"(?i)(id_rsa|\.ssh/|secrets\.yml|database\.yml|gitlab\.rb|\.env|/etc/passwd|/etc/shadow|config/secrets)";
let TraversalPattern = @"(\.\.\/|\.\.%2f|%2e%2e\/|%252e%252e)";
GitLabAccessLog_CL
| where TimeGenerated > ago(24h)
| where RequestUri_s matches regex @"(?i)/api/v[34]/projects/[^/\s]+/repository/commits"
| where RequestUri_s matches regex TraversalPattern
| where isempty(AuthorizationHeader_s) and isempty(PrivateTokenHeader_s) and isempty(JobTokenHeader_s)
| extend SensitiveTarget = RequestUri_s matches regex SensitivePattern
| summarize RequestCount=count(), TargetPaths=make_set(RequestUri_s), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated), AnySensitive=max(SensitiveTarget) by ClientIP_s, HttpStatusCode_d
| where RequestCount >= 1
| order by RequestCount desc

Sigma

title: GitLab Unauthenticated Path Traversal via Repository Commits API (CVE-2026-85706)
id: 8f3c1a2e-4b91-4d7a-9c6e-1a2b3c4d5e01
status: experimental
description: Detects unauthenticated requests to the GitLab repository commits API containing path traversal sequences, consistent with exploitation of CVE-2026-85706 (CVSS 10.0) allowing arbitrary file read on self-managed GitLab CE/EE.
references:
    - https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/
    - https://www.bleepingcomputer.com/news/security/gitlab-urges-users-to-patch-max-severity-path-traversal-flaw/
author: Threadlinqs Team
date: 2026-09-11
tags:
    - attack.initial-access
    - attack.t1190
    - attack.credential-access
    - attack.t1552.001
    - attack.t1552.004
    - cve.2026.85706
logsource:
    category: webserver
    product: gitlab
detection:
    selection_endpoint:
        cs-uri-query|contains: '/repository/commits'
    selection_traversal:
        cs-uri-query|contains:
            - '../'
            - '..%2f'
            - '%2e%2e/'
            - '%252e%252e'
    filter_authenticated:
        cs-uri-query|contains:
            - 'PRIVATE-TOKEN'
            - 'JOB-TOKEN'
        cs(Authorization)|contains: 'Bearer'
    condition: selection_endpoint and selection_traversal and not filter_authenticated
falsepositives:
    - Authorized vulnerability scanning or penetration testing against the GitLab instance
    - Security research/PoC validation traffic from an approved source
level: critical

Known false positives:

  • Authorized vulnerability scanning or penetration testing against the GitLab instance
  • Internal security research/PoC validation traffic from an approved source IP

Tuning notes: Allowlist known internal vulnerability-scanner source IPs and CI runners; narrow the sensitive-path regex to the organization's actual GitLab config/secrets locations to cut noise from legitimate deep repository paths.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • GitLab Repository Commits API Path Traversal — Exploitation (CVE-2026-85706) [KQL] · unlock with TL Creds
  • GitLab Duo Chat GraphQL Subscription Deserialization — Credential/Config Theft (CVE-2026-87719) [KQL] · unlock with TL Creds
  • Post-Compromise Lateral Movement & C2 Beacon from GitLab Worker Process (CVE-2026-88765 Context) [KQL] · unlock with TL Creds
  • GitLab Repository Commits API Path Traversal — Exploitation (CVE-2026-85706) [Sigma] · unlock with TL Creds
  • GitLab Duo Chat GraphQL Subscription Deserialization — Credential/Config Theft (CVE-2026-87719) [Sigma] · unlock with TL Creds
  • Post-Compromise Lateral Movement & C2 Beacon from GitLab Worker Process (CVE-2026-88765 Context) [Sigma] · unlock with TL Creds
  • GitLab Duo Chat GraphQL Subscription Deserialization — Credential/Config Theft (CVE-2026-87719) [SPL] · unlock with TL Creds
  • Post-Compromise Lateral Movement & C2 Beacon from GitLab Worker Process (CVE-2026-88765 Context) [SPL] · unlock with TL Creds

Indicators of compromise

As of 2026-09-14, Threadlinqs Intelligence tracks 48 indicators of compromise for TL-2026-2442.

48 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

GitLab.com and GitLab Dedicated are unaffected; neither CVE is listed in CISA's KEV catalog and no public PoC or in-the-wild exploitation has been confirmed for either flaw.

On September 10, 2026, GitLab shipped a critical patch release (versions 19.3.2, 19.2.6, and 19.1.8 for both Community Edition and Enterprise Edition) that fixes 18 vulnerabilities reported through GitLab's HackerOne bug-bounty program, headlined by two critical, unrelated-mechanism flaws.

CVE-2026-85706 (CVSS 3.1: 10.0, AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) is a path-traversal vulnerability in the repository commits API caused by improper path confinement combined with missing authentication enforcement (CWE-22 / CWE-306). It requires no account and no user interaction: an unauthenticated remote attacker can send crafted requests with traversal sequences to the commits endpoint to read arbitrary files from the underlying GitLab server, outside the intended repository boundary. Depending on server configuration this can expose application settings, secrets, authentication tokens, SSH private keys, and database credentials accessible to the GitLab process. It affects GitLab CE and EE from 18.7 through 19.1.7, 19.2.0 through 19.2.5, and 19.3.0 through 19.3.1. The researcher credited is HackerOne user 's3ntago'.

CVE-2026-87719 (CVSS 3.1: 9.9, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) is an insecure-deserialization weakness (CWE-502) in the GraphQL subscription serializer, affecting GitLab EE only (self-managed), from 18.3 through 19.1.7, 19.2.0 through 19.2.5, and 19.3.0 through 19.3.1. An authenticated user with access to the Duo Chat feature can submit a specially crafted GraphQL subscription argument to bypass serialization controls and trigger a server-side object lookup, exposing Advanced Search instance configuration and sensitive credentials. The researcher credited is HackerOne user 'kyyblin'.

The same September 10 advisory documents the remaining 16 vulnerabilities in the release across a full severity spread, notably: CVE-2026-88765 (CVSS 8.5, high) — a buffer overflow in a Unicode conversion wrapper reachable during Advanced Search indexing of an imported Git project export, letting an authenticated EE user achieve remote code execution by importing a maliciously crafted export (credited to HackerOne researcher 'joaxcar'; affects EE 12.3 through the same pre-19.3.2/19.2.6/19.1.8 ranges); and CVE-2026-79708 (CVSS 8.5, high) — insufficient scope validation letting an authenticated developer-role EE user execute a policy test pipeline to access protected CI/CD variables outside their intended scope (credited to HackerOne researcher 'yvvdwf'). Both of these, and the remaining medium/low-severity fixes (insecure deserialization-adjacent authorization bugs, GraphQL-complexity denial-of-service issues, XSS, and authorization-bypass flaws), are outside this threat record's declared CVE scope (CVE-2026-85706 and CVE-2026-87719) but are noted as sourced context establishing the breadth of the same patch release.

GitLab.com (SaaS) already runs the patched release and GitLab Dedicated customers require no action; only self-managed CE/EE installations are exposed. As of this research, neither CVE-2026-85706 nor CVE-2026-87719 appears in the CISA Known Exploited Vulnerabilities catalog, and no public proof-of-concept exploit code or in-the-wild exploitation has been confirmed for either flaw — cross-checked explicitly against the unrelated, separately-disclosed GitLab flaw CVE-2026-19478, which WAS actively exploited via watchTowr's honeypot network in August 2026, to avoid conflating the two. The exploitability assessment here is therefore theoretical/disclosed rather than actively exploited, notwithstanding the trivial, single-request nature of the unauthenticated file-read primitive once technical detail becomes public.

MITRE ATT&CK techniques by tactic:

Collection

T1005 Data from Local System; T1213 Data from Information Repositories; T1213.003 Data from Information Repositories: Code Repositories

Exfiltration

T1041 Exfiltration Over C2 Channel

Privilege Escalation

T1078 Valid Accounts

Persistence

T1136 Create Account

Initial Access

T1190 Exploit Public-Facing Application

Defense Evasion

T1211 Exploitation for Defense Evasion

Credential Access

T1528 Steal Application Access Token; T1552 Unsecured Credentials; T1552.001 Unsecured Credentials: Credentials In Files; T1552.004 Unsecured Credentials: Private Keys

Resource Development

T1587.004 Develop Capabilities: Exploits; T1588.005 Obtain Capabilities: Exploits; T1588.006 Obtain Capabilities: Vulnerabilities

Reconnaissance

T1594 Search Victim-Owned Websites; T1595.001 Active Scanning: Scanning IP Blocks; T1595.002 Active Scanning: Vulnerability Scanning; T1596.005 Search Open Technical Databases: Scan Databases

Remediation

Patches

  • GitLab CE/EE 19.3.2
  • GitLab CE/EE 19.2.6
  • GitLab CE/EE 19.1.8

Immediate actions

  • Upgrade self-managed GitLab CE/EE to 19.3.2, 19.2.6, or 19.1.8 immediately
  • Restrict network access to the GitLab instance (VPN/IP allowlist) as a temporary compensating control while patching is scheduled
  • Rotate application secrets, authentication tokens, SSH private keys, and database credentials if an internet-facing instance was unpatched and exposed

Workarounds

  • Restrict inbound network access to self-managed GitLab instances until patched; GitLab.com and GitLab Dedicated customers require no action

Longer-term hardening

  • Subscribe to GitLab security release announcements to track future patch releases
  • Restrict GitLab Duo Chat feature access to trusted, need-to-use accounts to reduce the authenticated attack surface for CVE-2026-87719
  • Monitor repository commits API and GraphQL subscription endpoints for anomalous or malformed request patterns
  • Require review/approval and malware scanning of Git project exports before import to reduce exposure to the related CVE-2026-88765 RCE-via-import vector

Affected and fixed versions

  • GitLab Inc. — GitLab Community Edition (CE)
    Vulnerable versions: 18.7-19.1.7 (CVE-2026-85706); 19.2.0-19.2.5; 19.3.0-19.3.1
    Fixed in: 19.1.8; 19.2.6; 19.3.2
  • GitLab Inc. — GitLab Enterprise Edition (EE)
    Vulnerable versions: 18.3-19.1.7 (CVE-2026-87719); 18.7-19.1.7 (CVE-2026-85706); 19.2.0-19.2.5; 19.3.0-19.3.1
    Fixed in: 19.1.8; 19.2.6; 19.3.2

Timeline

Last updated · 4 updates · revalidated 4× · latest source

Showing the 20 most recent tracked events.

  • watchTowr's Attacker Eye honeypot network records the first behavioral probes for CVE-2026-85706 approximately six hours after the patch release — earlier than the mass-scanning wave already on record for 2026-09-11 — indicating attackers rapidly reverse-engineered a working exploit from the patch diff.
  • GitLab's advisory documents the remaining 16 vulnerabilities in the same release, including CVE-2026-88765 (CVSS 8.5, buffer overflow in a Unicode conversion wrapper during Advanced Search indexing of a malicious Git project import, enabling authenticated RCE, credited to 'joaxcar') and CVE-2026-79708 (CVSS 8.5, policy test pipeline scope-validation bug exposing protected CI/CD variables, credited to 'yvvdwf').
  • GitLab confirms GitLab.com (SaaS) is already running the patched release and GitLab Dedicated customers are unaffected; only self-managed CE/EE instances require action.
  • GitLab credits HackerOne bug-bounty researchers 's3ntago' (CVE-2026-85706) and 'kyyblin' (CVE-2026-87719) for responsible disclosure.
  • GitLab's patch-release documentation publishes full CVSS 3.1 vectors: 10.0 for CVE-2026-85706 and 9.9 for CVE-2026-87719, alongside exact affected version ranges.
  • GitLab releases versions 19.3.2, 19.2.6, and 19.1.8 for CE and EE, fixing 18 vulnerabilities including CVE-2026-85706 and CVE-2026-87719.
  • watchTowr publishes its 'Rapid Reaction' technical analysis identifying the Workhorse/Puma decoding-mismatch root cause; Horizon3.ai releases a NodeZero Rapid Response validation module.
  • CISA adds CVE-2026-85706 to its Known Exploited Vulnerabilities catalog, citing confirmed active exploitation and invoking BOD 26-04.
  • watchTowr's Attacker Eye global honeypot network records the first behavioral probes for CVE-2026-85706 at 06:00 UTC, roughly 24 hours after disclosure.
  • Follow-up research explicitly distinguishes this disclosure from the separate, actively-exploited GitLab flaw CVE-2026-19478 (exploited via watchTowr's honeypot network in August 2026); no security vendor has reported in-the-wild exploitation of CVE-2026-85706 or CVE-2026-87719 as of September 11, 2026.
  • Research confirms neither CVE-2026-85706 nor CVE-2026-87719 appears in CISA's Known Exploited Vulnerabilities catalog, and no public proof-of-concept exploit code exists for either flaw as of publication.
  • cybersecuritynews.com, GBHackers, cyberpress.org, and securityonline.info publish technical breakdowns of the two critical CVEs, also noting the third high-severity RCE flaw (CVE-2026-88765) patched in the same release.
  • BleepingComputer reports on the critical patch release, urging self-managed GitLab administrators to upgrade immediately.
  • Independent public proof-of-concept exploits (guneykabel/cve-2026-85706 and a Python script by jithinkrishnanrs) are published on GitHub, automating the Workhorse-bypass technique.
  • NVD publishes the formal CVE-2026-85706 record with CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N and CWE-22 classification.
  • The Hacker News, BleepingComputer, SecurityWeek, and other outlets report on the CISA KEV addition and confirm in-the-wild scanning activity.
  • Exploitation activity reported to have progressed from reconnaissance probing to successful exfiltration of GitLab configuration files and SSH credentials from vulnerable internet-facing instances over the weekend following disclosure.
  • Rapid7 publishes an Emerging Threat Response blog on CVE-2026-85706, documenting active-exploitation status and patch guidance.
  • CISA BOD 26-04 remediation deadline: U.S. federal civilian agencies must have applied mitigations, completed forensic triage, or discontinued use of unpatched GitLab instances.
  • Rapid7 ships CVE-2026-85706 detection checks to InsightVM, Nexpose, and Exposure Command customers in its September 15 content release, distinct from the September 14 Rapid7 ETR blog already on record.

Update history

Sources cited

Other reports on CVE-2026-85706

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 9 sources; published ; last updated .

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats