Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25055: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in n8n-io n8n

0
High
VulnerabilityCVE-2026-25055cvecve-2026-25055cwe-22
Published: Wed Feb 04 2026 (02/04/2026, 16:47:47 UTC)
Source: CVE Database V5
Vendor/Project: n8n-io
Product: n8n

Description

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.

AI-Powered Analysis

AILast updated: 02/04/2026, 17:30:03 UTC

Technical Analysis

CVE-2026-25055 is a path traversal vulnerability (CWE-22) found in the n8n workflow automation platform prior to versions 1.123.12 and 2.4.0. The vulnerability occurs when workflows handle uploaded files and transfer them to remote servers using the SSH node without validating the file metadata, such as filenames or paths. This improper validation allows an attacker to craft file uploads that include path traversal sequences (e.g., ../) to write files outside the intended directories on the remote server. Because the SSH node executes file transfers remotely, this can lead to files being placed in sensitive locations, potentially enabling remote code execution if malicious payloads are written to executable paths. Exploitation requires the attacker to be unauthenticated but have knowledge of existing workflows that process file uploads and access to unauthenticated upload endpoints. The vulnerability is mitigated by validating and sanitizing file paths before transfer and by restricting access to upload endpoints. The issue has been addressed in n8n versions 1.123.12 and 2.4.0. The CVSS 4.0 score is 7.1 (high), reflecting network attack vector, low attack complexity, no privileges or user interaction required, but with high scope and impact on confidentiality, integrity, and availability. No known exploits have been reported in the wild as of the publication date.

Potential Impact

For European organizations, this vulnerability poses a significant risk especially for those leveraging n8n for automated workflows involving file uploads and remote SSH transfers. Successful exploitation could allow attackers to write arbitrary files to critical locations on remote servers, potentially leading to remote code execution, data compromise, or disruption of services. This could impact confidentiality, integrity, and availability of systems and data. Organizations in sectors with high automation reliance, such as finance, manufacturing, and critical infrastructure, may face operational disruptions or data breaches. The unauthenticated nature of the attack vector increases risk, particularly if upload endpoints are exposed to the internet without proper access controls. The potential for lateral movement and persistence through remote code execution elevates the threat level. While no active exploits are known, the presence of this vulnerability in widely used automation tools necessitates urgent remediation to prevent future attacks.

Mitigation Recommendations

1. Upgrade all n8n instances to versions 1.123.12 or 2.4.0 or later to ensure the vulnerability is patched. 2. Restrict access to file upload endpoints by implementing strong authentication and network-level controls such as IP whitelisting or VPN access. 3. Implement rigorous validation and sanitization of all file metadata, especially filenames and paths, within workflows before files are transferred to remote servers. 4. Review and audit existing workflows that use the SSH node for file transfers to identify and remediate any unsafe handling of file paths. 5. Employ monitoring and alerting on unusual file system changes or SSH activity on remote servers to detect potential exploitation attempts. 6. Conduct regular security assessments and penetration testing focused on automation platforms and their exposed endpoints. 7. Educate developers and administrators on secure workflow design and the risks of unauthenticated file uploads. 8. Use network segmentation to isolate critical systems and limit the impact of potential compromises.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-28T14:50:47.888Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69837ea2f9fa50a62f9d191e

Added to database: 2/4/2026, 5:15:14 PM

Last enriched: 2/4/2026, 5:30:03 PM

Last updated: 2/6/2026, 7:50:42 PM

Views: 35

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats