The vulnerability lies in the Git node of n8n. It allows the node to execute local git configuration values that are not sanitized, which leads to arbitrary command execution as the n8n process user. The flaw is a command injection issue (CWE‑78). An attacker must first inject a malicious git configuration value into a repository and then trigger any Git node operation against that repository to cause the execution. The vulnerability is not directly reachable through the node’s own configuration controls and therefore requires a separate file‑write ability to place the malicious value.

All installations of n8n version 1.x before 1.123.69 and 2.x before 2.33.4 or 2.34.1 are affected. The product is maintained by n8n‑io, and the exploitability depends on the specific deployment version used.

The CVSS score of 7.7 indicates high severity, but the EPSS score is not available and the vulnerability is not listed in CISA’s KEV catalog. Nonetheless, if an attacker can write to a repository, the flaw permits them to execute arbitrary commands with the privileges of the n8n service account. The requirement of a separate file‑write vulnerability lowers the attack probability compared to a purely remote exploit, yet the potential impact remains significant.