CVE-2025-62726: N8n Remote Code Execution Vulnerability

HIGH
Advisory Identifier: GHSA-xgp7-7qjq-vg47
CVSS 8.8
CWE-829
Published
Advisory Summary

CVE-2025-62726 is a HIGH (CVSS 8.8) remote code execution vulnerability (CWE-829: Inclusion of Functionality from Untrusted Control Sphere) affecting N8n libraries in the npm ecosystem. The issue involves n8n vulnerable to remote code execution via git node pre-commit hook. Remediation is available by upgrading affected packages to version 1.113.0.

CVE-2025-62726 at a Glance

CVE Identifier CVE-2025-62726
GHSA Identifier GHSA-xgp7-7qjq-vg47
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-829: Inclusion of Functionality from Untrusted Control Sphere
Affected Product N8n
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-62726

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.113.0
npm install n8n@1.113.0
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-2025-62726, 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.113.0), 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-829: Inclusion of Functionality from Untrusted Control Sphere, where the product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. 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 A remote code execution vulnerability exists in the Git Node component available in both Cloud and Self-Hosted versions of n8n. When a malicious actor clones a remote repository containing a pre-commit hook, the subsequent use of the Commit operation in the Git Node can inadvertently trigger the hook’s execution. This allows attackers to execute arbitrary code within the n8n environment, potentially compromising the system and any connected credentials or workflows. All users with workflows that utilize the Git Node to clone untrusted repositories are affected. ### Patches The vulnerability was addressed in v1.113.0 (n8n-io/n8n#19559), which introduces a new environment variable: `N8N_GIT_NODE_DISABLE_BARE_REPOS`. For self-hosted deployments, it is strongly recommended to set this variable to `true` to mitigate the risk of executing malicious Git hooks. ### Workarounds To reduce risk prior to upgrading: - Avoid cloning or interacting with untrusted repositories using the Git Node. - Disable or restrict the use of the Git Node in workflows where repository content cannot be fully trusted.

CVE-2025-62726 Affected N8n Versions

1 component(s)
Fixed Versions:
1.113.0
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm
< 1.113.0
1.113.0

References

Frequently Asked Questions

What is CVE-2025-62726?
CVE-2025-62726 is a security vulnerability in N8n involving n8n Vulnerable to Remote Code Execution via Git Node Pre-Commit Hook under CWE-829: Inclusion of Functionality from Untrusted Control Sphere.
Which N8n versions are affected?
Affected versions include releases prior to 1.113.0 across affected packages: n8n.
What version fixes CVE-2025-62726?
Upgrading to 1.113.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 1.113.0. Upgrade your dependency to 1.113.0 or later.
What is the CVSS score of CVE-2025-62726?
CVE-2025-62726 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2025-62726?
CVE-2025-62726 is classified under CWE-829: Inclusion of Functionality from Untrusted Control Sphere (The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.).
How can I check npm dependencies for CVE-2025-62726?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xgp7-7qjq-vg47",
  "modified" : "2025-10-30T19:54:37Z",
  "published" : "2025-10-30T17:04:26Z",
  "aliases" : [ "CVE-2025-62726" ],
  "summary" : "n8n Vulnerable to Remote Code Execution via Git Node Pre-Commit Hook",
  "details" : "### Impact\nA remote code execution vulnerability exists in the Git Node component available in both Cloud and Self-Hosted versions of n8n. When a malicious actor clones a remote repository containing a pre-commit hook, the subsequent use of the Commit operation in the Git Node can inadvertently trigger the hook’s execution.\n\nThis allows attackers to execute arbitrary code within the n8n environment, potentially compromising the system and any connected credentials or workflows.\n\nAll users with workflows that utilize the Git Node to clone untrusted repositories are affected.\n\n### Patches\nThe vulnerability was addressed in v1.113.0 (n8n-io/n8n#19559), which introduces a new environment variable: `N8N_GIT_NODE_DISABLE_BARE_REPOS`. For self-hosted deployments, it is strongly recommended to set this variable to `true` to mitigate the risk of executing malicious Git hooks.\n\n### Workarounds\nTo reduce risk prior to upgrading:\n\n- Avoid cloning or interacting with untrusted repositories using the Git Node.\n- Disable or restrict the use of the Git Node in workflows where repository content cannot be fully trusted.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.113.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-xgp7-7qjq-vg47"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-62726"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/pull/19559"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/commit/5bf3db5ba84d3195bbe11bbd3c62f7086e090997"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-829" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-10-30T17:04:26Z",
    "nvd_published_at" : "2025-10-30T17:15:39Z"
  }
}