7.1

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-25055

CVE-2026-25055: n8n Arbitrary File Write on Remote Systems via SSH Node

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-25055

CVE-2026-25055:

7.1

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
n8n	npm	>= 2.0.0, < 2.4.0	2.4.0
n8n	npm	< 1.123.12	1.123.12

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is a path traversal issue in the n8n SSH node, which allows an unauthenticated attacker to write files to arbitrary locations on a remote system. The root cause is the failure to sanitize user-provided filenames before using them in file transfer operations.

The analysis of the security patches (commits 528ad6b982d0519ec170e172f57b7fdbbe175230 and e0baf48c6a54808f6dbca8cb352bfa306092c223) pinpoints the exact code locations that were fixed.

Ssh.execute: This is the primary vulnerable function. Located in packages/nodes-base/nodes/Ssh/Ssh.node.ts, this method's 'upload' operation constructed a remote file path by concatenating a base directory with the raw filename from the input data. An attacker could craft a filename like ../../../tmp/pwned.txt to break out of the intended directory. The fix involves using a new sanitizeFilename function to strip all directory components from the filename before it is used by the ssh.putFile method.
copyBinaryFile: This utility function, found in packages/core/src/execution-engine/node-execution-context/utils/binary-helper-functions.ts, was also patched. It was identified that this function also handled filenames insecurely by assigning them without sanitization. While not the direct entry point for the SSH node exploit, fixing it provides defense-in-depth and prevents similar vulnerabilities in other nodes or workflows that might rely on this function.

The mitigation strategy was to introduce a sanitizeFilename utility that leverages path.basename to ensure only the filename part of a path is ever used, effectively neutralizing the path traversal threat.

Vulnerable functions

Ssh.execute

packages/nodes-base/nodes/Ssh/Ssh.node.ts

The `execute` method of the `Ssh` class is responsible for handling the file upload operation. The vulnerability lies in the fact that it directly used the user-provided filename (`fileName` or `binaryData.fileName`) to construct the destination path on the remote server for the `ssh.putFile` operation. This allowed an attacker to include path traversal characters (e.g., `../`) in the filename, causing the file to be written to an arbitrary location on the remote filesystem.

copyBinaryFile

packages/core/src/execution-engine/node-execution-context/utils/binary-helper-functions.ts

The `copyBinaryFile` function is a helper function for handling binary file data within n8n workflows. It was vulnerable because it assigned the `fileName` property directly from a user-controlled `fileName` parameter or by extracting it from a `filePath` without proper sanitization. This could lead to path traversal vulnerabilities in any part of the application that uses this function to process files. The patch applies the `sanitizeFilename` function to prevent this.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.