GitHub Advisoryadvisory · npm

GHSA-rcv6-pvrj-4xcg n8n: Authenticated code execution in the n8n Git node

HIGH Published 2026-07-22 Modified 2026-07-22 Official page ↗
Ecosystem
npm
Packages
n8n
Severity
High
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Weaknesses
CWE-78
Reviewed
2026-07-22

Affected packages

• npm n8n: < 1.123.67 → fixed in 1.123.67 • npm n8n: >= 2.32.0, < 2.32.1 → fixed in 2.32.1 • npm n8n: >= 2.0.0-rc.0, < 2.31.5 → fixed in 2.31.5

Description

Impact Authenticated n8n users with rights to create and execute workflows could achieve code execution on the n8n host. Using the Git node, under the default `git` security settings, by staging a crafted local repository, an attacker could cause `git` to run hooks, executing arbitrary commands as the n8n process user. Both self-hosted and cloud instances are affected where authenticated users can create and execute workflows using the Git node. Patches The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. 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. • Restrict network egress from the n8n instance to limit the impact of arbitrary code execution. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Related

Weakness · CWE (1)

  • CWE-78 Improper Neutralization of Special Elements used in an OS Command weakness

References