CVE-2025-68697: Self-hosted n8n has Legacy Code node that enables arbitrary file read/write
Impact
In self-hosted n8n instances where the Code node runs in legacy (non-task-runner) JavaScript execution mode, authenticated users with workflow editing access can invoke internal helper functions from within the Code node.
This allows a workflow editor to perform actions on the n8n host with the same privileges as the n8n process, including:
- Reading files from the host filesystem (subject to any file-access restrictions configured on the instance and OS/container permissions) - Writing files to the host filesystem (subject to the same restrictions)
Starting with n8n version 1.2.1, access to files in the n8n home directory (.n8n) is blocked by default. However, this does not restrict access to other parts of the filesystem unless additional file access limitations are configured.
Patches
- Upgrade to n8n version 2.0.0 or later, where task runners are enabled by default for Code node execution. - On n8n version 1.71.0 and above, enable task runners by setting N8NRUNNERSENABLED=true.
Workarounds
If you cannot immediately migrate to task runners:
- Limit file operations by setting N8NRESTRICTFILEACCESSTO to a dedicated directory (e.g., ~/.n8n-files) and ensure it contains no sensitive data. - Keep N8NBLOCKFILEACCESSTON8NFILES=true (default) to block access to .n8n and user-defined config files. - If workflow editors are not fully trusted, consider disabling high-risk nodes (including the Code node) using NODESEXCLUDE.
Resources
- n8n Docs: Task runners - n8n Docs: Task runner environment variables - n8n Docs: Security environment variables - n8n Docs: v2.0 breaking changes
Other sources
n8n is an open source workflow automation platform. Prior to version 2.0.0, in self-hosted n8n instances where the Code node runs in legacy (non-task-runner) JavaScript execution mode, authenticated users with workflow editing access can invoke internal helper functions from within the Code node. This allows a workflow editor to perform actions on the n8n host with the same privileges as the n8n process, including: reading files from the host filesystem (subject to any file-access restrictions configured on the instance and OS/container permissions), and writing files to the host filesystem (subject to the same restrictions). This issue has been patched in version 2.0.0. Workarounds for this issue involve limiting file operations by setting N8NRESTRICTFILEACCESSTO to a dedicated directory (e.g., ~/.n8n-files) and ensure it contains no sensitive data, keeping N8NBLOCKFILEACCESSTON8NFILES=true (default) to block access to .n8n and user-defined config files, and disabling high-risk nodes (including the Code node) using NODESEXCLUDE if workflow editors are not fully trusted.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.0.0 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.0.0 - Configuration
Disable high-risk nodes, including the Code node, when workflow editors are not fully trusted.
n8n NODES_EXCLUDE = Code - Configuration
Keep blocking access to .n8n and user-defined configuration files.
n8n N8N_BLOCK_FILE_ACCESS_TO_N8N_FILES = true - Configuration
Restrict file operations to a dedicated directory such as ~/.n8n-files, and ensure it contains no sensitive data.
n8n N8N_RESTRICT_FILE_ACCESS_TO = ~/.n8n-files - Configuration
On n8n version 1.71.0 and above, enable task runners.
n8n N8N_RUNNERS_ENABLED = true
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68697?
CVE-2025-68697 has been classified with a moderate severity level due to the potential for unauthorized actions on the host.
How do I fix CVE-2025-68697?
To fix CVE-2025-68697, upgrade to version 2.0.1 or later of the n8n package.
Who is affected by CVE-2025-68697?
CVE-2025-68697 affects self-hosted n8n instances running version 2.0.0 and below.
What can an attacker do with CVE-2025-68697?
An attacker can exploit CVE-2025-68697 to invoke internal helper functions and perform unauthorized actions on the n8n host.
Is authentication required to exploit CVE-2025-68697?
Yes, successful exploitation of CVE-2025-68697 requires authentication as an authenticated user with workflow editing access.