CVE-2026-33724

n8n is an open source workflow automation platform. Prior to version 2.5.0, 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). The issue has been fixed in n8n version 2.5.0. Users should upgrade to this version or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Disable the Source Control feature if it is not actively required, and/or 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.

An attacker with network positioning on the path between the n8n instance and its remote git server—achievable via ARP poisoning on the same subnet, a compromised cloud routing layer, or BGP manipulation—intercepts the SSH handshake when n8n pulls workflow updates. Because StrictHostKeyChecking is disabled, n8n silently accepts the attacker's fraudulent host key. The attacker serves a modified repository containing production workflows with injected malicious steps: an added HTTP Request node that forwards all LLM completions to an external endpoint, a modified AI Agent node with a rewritten system prompt introducing a persistent indirect prompt injection, or a Code node that exfiltrates environment variables including API keys for downstream AI services. These poisoned workflows deploy transparently and execute on every subsequent trigger, potentially for weeks before discovery.