Skip to content
n8nGHSA-j4p8-h8mh-rh8q

Self-hosted n8n has Legacy Code node that enables arbitrary file read/write

High7.1CVE-2025-68697 · Published Dec 26, 2025 · updated Dec 31, 2025

GitHub advisory

Affected versions

PackageAffectedFixed in
n8n
npm
>= 1.2.1, < 2.0.02.0.0
Details and references

### 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 `N8N_RUNNERS_ENABLED=true`. ### Workarounds If you cannot immediately migrate to task runners: - Limit file operations by setting `N8N_RESTRICT_FILE_ACCESS_TO` to a dedicated directory (e.g., `~/.n8n-files`) and ensure it contains no sensitive data. - Keep `N8N_BLOCK_FILE_ACCESS_TO_N8N_FILES=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 `NODES_EXCLUDE`. ### Resources - n8n Docs: [Task runners](https://docs.n8n.io/hosting/configuration/task-runners/) - n8n Docs: [Task runner environment variables](https://docs.n8n.io/hosting/configuration/environment-variables/task-runners/) - n8n Docs: [Security environment variables](https://docs.n8n.io/hosting/configuration/environment-variables/security/#security-environment-variables) - n8n Docs: [v2.0 breaking changes](https://docs.n8n.io/2-0-breaking-changes/#enable-task-runners-by-default)

CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Severity from
GitHub (reviewed advisory)
Weakness
CWE-269, CWE-749
Also known as
CVE-2025-68697

More n8n advisories

All n8n
DateAdvisory
Dec 262025n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox
CVE-2025-61914High7.3fixed in 1.114.0
Dec 262025n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node
CVE-2025-68668Critical9.9fixed in 2.0.0
Dec 222025n8n Vulnerable to Remote Code Execution via Expression Injection
CVE-2025-68613Critical9.9fixed in 1.120.4, 1.121.1
Jan 6n8n Vulnerable to RCE via Arbitrary File Write
CVE-2026-21877Critical9.9fixed in 1.121.3
Jan 7n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling
CVE-2026-21858Critical10.0fixed in 1.121.0
Jan 7n8n's Missing Stripe-Signature Verification Allows Unauthenticated Forged Webhooks
CVE-2026-21894Medium6.5fixed in 2.2.2

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.