Summary
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
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.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-25055? CVE-2026-25055 is a high-severity path traversal vulnerability in n8n (npm), affecting versions >= 2.0.0, < 2.4.0. It is fixed in 2.4.0, 1.123.12. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of n8n are affected by CVE-2026-25055? n8n (npm) versions >= 2.0.0, < 2.4.0 is affected.
- Is there a fix for CVE-2026-25055? Yes. CVE-2026-25055 is fixed in 2.4.0, 1.123.12. Upgrade to this version or later.
- Is CVE-2026-25055 exploitable, and should I be worried? Whether CVE-2026-25055 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-25055 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-25055?
- Upgrade
n8nto 2.4.0 or later - Upgrade
n8nto 1.123.12 or later
- Upgrade