| Package | Affected versions | Patched versions |
|---|---|---|
| n8n | ≥ 2.0.0, < 2.37.7≥ 2.38.0, < 2.38.2< 1.123.76 | 2.37.72.38.21.123.76 |
| n8n | ≥ 2.0.0, < 2.37.7≥ 2.38.0, < 2.38.2< 1.123.76 | 2.37.72.38.21.123.76 |
The Git node validated the repository that a fetch or pull targeted, but setUpstream wrote a branch.<name>.remote value into the repository's own configuration without validating it. A subsequent fetch or pull resolved the remote from that configuration rather than from the checked parameter, so an authenticated user with workflow-edit permission could point it at any local repository the n8n process could read and receive its contents. The patch validates the branch remote configuration on the same terms as the repository parameter.
The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
n8n-nodes-base.git to the NODES_EXCLUDE environment variable.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free