Skip to content

Back to the catalog

CVE-2026-85706: Critical GitLab Path Traversal Exploited in the Wild
rapid7.comadvisory

CVE-2026-85706: Critical GitLab Path Traversal Exploited in the Wild

GitLab patched CVE-2026-85706, a critical (CVSS 10.0) path traversal flaw (CWE-22) in the repository commits API that lets an unauthenticated attacker read arbitrary files from self-managed GitLab CE/EE instances; CISA added it to the KEV catalog on September 11, 2026 due to active exploitation, with a remediation deadline of September 14. The same patch release fixes CVE-2026-87719, a critical insecure deserialization bug (CWE-502) letting an authenticated Duo Chat user exfiltrate Advanced Search configs and credentials via a crafted GraphQL subscription argument, plus 17 other vulnerabilities. Rapid7 recommends emergency patching and post-patch compromise checks given confirmed in-the-wild exploitation.

TL;DR Unauthenticated, actively exploited path-traversal CVE in GitLab's commits API (CVSS 10.0) is now KEV-listed; emergency patch to 19.3.2+ required.
Document

What it is

GitLab's September 10, 2026 critical patch release for CE/EE, addressed by Rapid7's analysis. The headline fix, CVE-2026-85706 (CVSS 10.0, CWE-22 path traversal in the repository commits API), is already covered in the catalog summary. What the summary omits is the deployment and remediation mechanics engineers need to actually execute the fix.

Preconditions / Affected

All self-managed deployment types are affected: Omnibus, source-code installs, and Helm chart deployments. GitLab.com is already patched, and GitLab Dedicated customers need take no action — only self-managed CE/EE is exposed.

What to do

  • Upgrade self-managed instances to a fixed version immediately, outside normal patch cycles.
  • The update includes database migrations. Single-node installations will experience downtime during migration; multi-node deployments should use GitLab's zero-downtime upgrade procedure.
  • Of the fixed releases, only version 19.3.2 includes post-deployment migrations — relevant for upgrade planning/sequencing on multi-node setups.
  • Rapid7 InsightVM/Nexpose/Exposure Command customers can check exposure to CVE-2026-85706 via a vulnerability check in the September 15 content release.
  • Organizations subject to CISA BOD 26-04 must follow the forensic triage requirements tied to this KEV entry, not just patch-and-move-on.
flowchart TD
    A[Self-managed GitLab CE/EE] --> B{Deployment type?}
    B -->|Single-node| C[Upgrade with downtime during DB migration]
    B -->|Multi-node| D[Zero-downtime upgrade procedure]
    C --> E{Target version 19.3.2?}
    D --> E
    E -->|Yes| F[Post-deployment migrations also required]
    E -->|No| G[Standard migration only]

Caveats

At time of publication, only CVE-2026-85706 is confirmed exploited in the wild — the deserialization bug (CVE-2026-87719) and the other 17 fixed vulnerabilities are not. Rapid7's detection content for CVE-2026-85706 was not yet live at publication (scheduled for the September 15 content release).

Organisations named here

  • CWE-502

CVEs named here

  • CVE-2026-85706
  • CVE-2026-87719

Technologies named here

  • GitLab Community Edition
  • Exposure Command
  • GitLab Enterprise Edition
  • InsightVM
  • GitLab.com
  • Nexpose
  • GitLab Dedicated
  • GitLab
  • CVSS
  • GraphQL
  • CISA KEV

Techniques named here

  • Path traversal
  • Insecure deserialization

Also named here

  • CWE-22