MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2026-33724

n8n's Source Control SSH Configuration Uses StrictHostKeyChecking=no

CVE-2026-33724 ยท 2026-03-25 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the source)
Technique
Information exposure
Affected
n8n (npm)
CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS
0.3% chance of exploitation in 30 days

How it works, in short

Source control SSH disables host key verification, which lets a network attacker impersonate the Git server and intercept repository data. (Our summary, written by a model. The source text is below.)

Details

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.

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.