CVE-2026-33724 n8n's Source Control SSH Configuration Uses StrictHostKeyChecking=no
Attackers can intercept SSH connections in n8n's Source Control feature to inject malicious content or steal data due to disabled host key verification.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-33724?
CVE-2026-33724 is a medium-severity vulnerability in N8n N8n, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-639
Which versions are affected by CVE-2026-33724?
2 open source packages ship an affected version, including n8n. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
n8n npm | All versions | 2.5.0 |
n8n npm | All versions | 2.5.0 |
Products include N8n N8n.
How do I fix CVE-2026-33724?
Upgrade n8n to 2.5.0 or later.
Is CVE-2026-33724 being exploited?
There is no known exploitation of CVE-2026-33724 in the wild and no public exploit code.
Other vulnerabilities in N8n N8n
- CVE-2025-68613 n8n Improper Control of Dynamically-Managed Code Resources
- CVE-2026-21877 n8n is vulnerable to Remote Code Execution via Arbitrary File Write
- CVE-2026-21858 n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling
- CVE-2026-1470 n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution
- CVE-2025-68668 n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node
Sources
Also known as GHSA-43v7-fp2v-68f6.