CVE-2026-25055: n8n Arbitrary File Write on Remote Systems via SSH Node
Impact When workflows process uploaded files and transfer them to remote servers via the SSH node without validating their metadata the vulnerability can lead to files being written to unintended locations on those remote systems potentially leading to remote code execution on those systems.
As a prerequisites an unauthenticated attacker needs knowledge of such workflows existing and the endpoints for file uploads need to be unauthenticated.
Patches The issue has been fixed in n8n version 2.4.0 and 1.123.12. 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 or restrict access to workflows that accept file uploads via webhooks and transfer them via SSH. - Enable webhook authentication on all endpoints that handle file uploads. - Review usage of SSH credentials and consider rotating SSH credentials if in doubt. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Resources - n8n Documentation — Blocking nodes — how to globally disable specific nodes
---
n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Other sources
n8n is an open source workflow automation platform. Prior to versions 1.123.12 and 2.4.0, when workflows process uploaded files and transfer them to remote servers via the SSH node without validating their metadata the vulnerability can lead to files being written to unintended locations on those remote systems potentially leading to remote code execution on those systems. As a prerequisites an unauthenticated attacker needs knowledge of such workflows existing and the endpoints for file uploads need to be unauthenticated. This issue has been patched in versions 1.123.12 and 2.4.0.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25055?
The severity of CVE-2026-25055 is considered high due to the potential for arbitrary file writes on remote systems.
How do I fix CVE-2026-25055?
To fix CVE-2026-25055, upgrade n8n to version 1.123.12 or version 2.4.0.
What versions of n8n are affected by CVE-2026-25055?
CVE-2026-25055 affects n8n versions up to 1.123.12 and versions between 2.0.0 and 2.4.0.
What are the implications of exploiting CVE-2026-25055?
Exploiting CVE-2026-25055 can lead to unauthorized file writing on remote servers, potentially compromising those systems.
Is n8n still secure if I haven't updated for CVE-2026-25055?
If you have not updated n8n to the patched versions, it remains vulnerable to CVE-2026-25055 and should be prioritized for updating.