n8n before 1.123.69 Remote Code Execution via Git Node Configuration Values
n8n-io n8n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n-io n8n
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n before 1.123.69 (and 2.x before 2.33.4 / 2.34.1) contains a code execution vulnerability in the Git node. The Git node executed certain repository-local git configuration values without neutralizing them, so any subsequent Git node operation against a repository containing a malicious value would execute it as the n8n process user. This is not reachable through the Git node's own configuration controls and requires a separate file-write vulnerability elsewhere to plant the malicious value.
From the CVE record · VulnCheck
The Git node in affected n8n versions can execute malicious repository-local Git configuration values as the n8n process user. An attacker must first plant such a value through a separate file-write vulnerability; a subsequent Git node operation against that repository triggers execution. The value cannot be planted through the Git node’s own configuration controls.
Engineers running n8n before 1.123.69 or affected 2.x versions before 2.33.4 / 2.34.1 should check their deployments.