n8n before 1.123.73 Remote Code Execution via Git Node
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 versions before 1.123.73, 2.35.4, and 2.36.2 contain a remote code execution vulnerability in the Git node. The node reset a fixed list of command-bearing configuration keys before each operation, but that list did not cover the content-filter and merge-driver key families. A repository with local configuration setting one of those keys together with a matching attribute pattern causes git to execute the configured command during an ordinary Add, Commit, Checkout, or Pull operation. The command runs as the n8n process user.
From the CVE record · VulnCheck
The n8n Git node does not reset certain command-bearing Git configuration keys before operations. If a repository has a local content-filter or merge-driver configuration and a matching attribute pattern, an ordinary Add, Commit, Checkout, or Pull can execute the configured command as the n8n process user.
Teams running n8n versions before 1.123.73, 2.35.4, or 2.36.2 should check their installations.