CVE-2026-86995: n8n Git Node Branch.<name>.remote Config Key Vulnerability

MODERATE
Advisory Identifier: GHSA-qgpw-8g46-w95v
Share
CWE-73 CWE-22
Published
Advisory Summary

CVE-2026-86995 is a MODERATE git node branch.<name>.remote config key vulnerability (CWE-73: External Control of File Name or Path) affecting n8n libraries in the npm ecosystem. The issue involves git node branch.<name>.remote config key bypasses sandbox path restriction, enabling local git repository read. Remediation is available by upgrading affected packages to version 1.123.76, 2.38.2, 2.37.7.

CVE-2026-86995 at a Glance

CVE Identifier CVE-2026-86995
GHSA Identifier GHSA-qgpw-8g46-w95v
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-73: External Control of File Name or Path
Affected Product n8n
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-86995

To remediate this vulnerability, upgrade all affected n8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 1.123.76 
npm install n8n@1.123.76
n8n fixed: 2.38.2 
npm install n8n@2.38.2
n8n fixed: 2.37.7 
npm install n8n@2.37.7
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-86995, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of n8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.123.76), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-73: External Control of File Name or Path, where the product allows user input to control or influence paths or file names that are used in filesystem operations. In n8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact The Git node validated the repository that a fetch or pull targeted, but `setUpstream` wrote a `branch.<name>.remote` value into the repository's own configuration without validating it. A subsequent fetch or pull resolved the remote from that configuration rather than from the checked parameter, so an authenticated user with workflow-edit permission could point it at any local repository the n8n process could read and receive its contents. The patch validates the branch remote configuration on the same terms as the repository parameter. ## Patches The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Disable the Git node by adding `n8n-nodes-base.git` to the `NODES_EXCLUDE` environment variable. - Ensure the n8n process runs under a dedicated low-privilege OS user account to limit the scope of any filesystem access. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

CVE-2026-86995 Affected n8n Versions

3 component(s)
Fixed Versions:
1.123.762.38.22.37.7
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm/n8n
npm
< 1.123.76
1.123.76
n8n
npm/n8n
npm
≥ 2.38.0
< 2.38.2
2.38.2
n8n
npm/n8n
npm
≥ 2.0.0
< 2.37.7
2.37.7

References

GitHub Advisory / Wiki ADVISORY
https://github.com/n8n-io/n8n/security/advisories/GHSA-qgpw-8g46-w95v
NVD — CVE-2026-86995 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-86995
n8n Source Repository REPOSITORY
https://github.com/n8n-io/n8n
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.76
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2

Frequently Asked Questions

What is CVE-2026-86995?
CVE-2026-86995 is a security vulnerability in n8n involving Git Node branch.<name>.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read under CWE-73: External Control of File Name or Path.
Which n8n versions are affected?
Affected versions include releases prior to 1.123.76, 2.38.2, 2.37.7 across affected packages: n8n.
What version fixes CVE-2026-86995?
Upgrading to 1.123.76, 2.38.2, 2.37.7 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 1.123.76, 2.38.2, 2.37.7. Upgrade your dependency to 1.123.76, 2.38.2, 2.37.7 or later.
What CWE is associated with CVE-2026-86995?
CVE-2026-86995 is classified under CWE-73: External Control of File Name or Path (The product allows user input to control or influence paths or file names that are used in filesystem operations.).
How can I check npm dependencies for CVE-2026-86995?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qgpw-8g46-w95v",
  "modified" : "2026-09-10T21:16:36Z",
  "published" : "2026-09-10T21:16:36Z",
  "aliases" : [ "CVE-2026-86995" ],
  "summary" : "n8n: Git Node branch.<name>.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read",
  "details" : "## Impact\n\nThe Git node validated the repository that a fetch or pull targeted, but `setUpstream` wrote a `branch.<name>.remote` value into the repository's own configuration without validating it. A subsequent fetch or pull resolved the remote from that configuration rather than from the checked parameter, so an authenticated user with workflow-edit permission could point it at any local repository the n8n process could read and receive its contents. The patch validates the branch remote configuration on the same terms as the repository parameter.\n\n## Patches\n\nThe issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Disable the Git node by adding `n8n-nodes-base.git` to the `NODES_EXCLUDE` environment variable.\n- Ensure the n8n process runs under a dedicated low-privilege OS user account to limit the scope of any filesystem access.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.123.76"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.38.0"
      }, {
        "fixed" : "2.38.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.37.7"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-qgpw-8g46-w95v"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-86995"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.76"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22", "CWE-73" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-10T21:16:36Z",
    "nvd_published_at" : "2026-09-08T22:19:18Z"
  }
}