n8n's Source Control SSH Configuration Uses StrictHostKeyChecking=no

Impact

When the Source Control feature is configured to use SSH, the SSH command used for git operations explicitly disabled host key verification. A network attacker positioned between the n8n instance and the remote Git server could intercept the connection and present a fraudulent host key, potentially injecting malicious content into workflows or intercepting repository data.

• This issue only affects instances where the Source Control feature has been explicitly enabled and configured to use SSH (non-default).

Patches

The issue has been fixed in n8n version 2.5.0. Users should upgrade to this version or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

• Disable the Source Control feature if it is not actively required.
• Restrict network access to ensure the n8n instance communicates with the Git server only over trusted, controlled network paths.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.