CVE-2026-25055: N8n N8n Vulnerable To Arbitrary File Vulnerability

HIGH
Advisory Identifier: GHSA-m82q-59gv-mcr9
Share
CWE-22
Published
Advisory Summary

CVE-2026-25055 is a HIGH n8n vulnerable to arbitrary file vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting N8n libraries in the npm ecosystem. The issue involves n8n vulnerable to arbitrary file write on remote systems via ssh node. Remediation is available by upgrading affected packages to version 1.123.12, 2.4.0.

CVE-2026-25055 at a Glance

CVE Identifier CVE-2026-25055
GHSA Identifier GHSA-m82q-59gv-mcr9
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product N8n
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-25055

To remediate this vulnerability, upgrade all affected N8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 1.123.12 
npm install n8n@1.123.12
n8n fixed: 2.4.0 
npm install n8n@2.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-25055, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of N8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.123.12), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In N8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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](https://docs.n8n.io/hosting/securing/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

CVE-2026-25055 Affected N8n Versions

2 component(s)
Fixed Versions:
1.123.122.4.0
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm/n8n
npm
< 1.123.12
1.123.12
n8n
npm/n8n
npm
≥ 2.0.0
< 2.4.0
2.4.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/n8n-io/n8n/security/advisories/GHSA-m82q-59gv-mcr9
NVD — CVE-2026-25055 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-25055
Security Fix Commit FIX COMMIT
https://github.com/n8n-io/n8n/commit/528ad6b982d0519ec170e172f57b7fdbbe175230
Security Fix Commit FIX COMMIT
https://github.com/n8n-io/n8n/commit/e0baf48c6a54808f6dbca8cb352bfa306092c223
N8n Source Repository REPOSITORY
https://github.com/n8n-io/n8n

Frequently Asked Questions

What is CVE-2026-25055?
CVE-2026-25055 is a security vulnerability in N8n involving n8n Vulnerable to Arbitrary File Write on Remote Systems via SSH Node under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which N8n versions are affected?
Affected versions include releases prior to 1.123.12, 2.4.0 across affected packages: n8n.
What version fixes CVE-2026-25055?
Upgrading to 1.123.12, 2.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 1.123.12, 2.4.0. Upgrade your dependency to 1.123.12, 2.4.0 or later.
What CWE is associated with CVE-2026-25055?
CVE-2026-25055 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check npm dependencies for CVE-2026-25055?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m82q-59gv-mcr9",
  "modified" : "2026-02-04T19:36:29Z",
  "published" : "2026-02-04T19:36:29Z",
  "aliases" : [ "CVE-2026-25055" ],
  "summary" : "n8n Vulnerable to Arbitrary File Write on Remote Systems via SSH Node",
  "details" : "## Impact\nWhen 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.\n\nAs a prerequisites an unauthenticated attacker needs knowledge of such workflows existing and the endpoints for file uploads need to be unauthenticated.\n\n## Patches\nThe 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.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Disable or restrict access to workflows that accept file uploads via webhooks and transfer them via SSH.\n- Enable webhook authentication on all endpoints that handle file uploads.\n- Review usage of SSH credentials and consider rotating SSH credentials if in doubt.\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.\n\n## Resources\n- [n8n Documentation — Blocking nodes](https://docs.n8n.io/hosting/securing/blocking-nodes/) — how to globally disable specific nodes\n\n---\n\nn8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility.\n\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.4.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.123.12"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-m82q-59gv-mcr9"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-25055"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/commit/528ad6b982d0519ec170e172f57b7fdbbe175230"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/commit/e0baf48c6a54808f6dbca8cb352bfa306092c223"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-04T19:36:29Z",
    "nvd_published_at" : "2026-02-04T17:16:23Z"
  }
}