# CVE-2025-68697: Self-hosted n8n has Legacy Code node that enables arbitrary file read/write


- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Dec 2025
- **Updated:** 26 Dec 2025
- **Also known as:** GHSA-j4p8-h8mh-rh8q

## What is CVE-2025-68697?

CVE-2025-68697 is a high-severity vulnerability in N8n N8n, published on 26 Dec 2025. 

### Official description

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 N8N_RESTRICT_FILE_ACCESS_TO to a dedicated directory (e.g., ~/.n8n-files) and ensure it contains no sensitive data, keeping N8N_BLOCK_FILE_ACCESS_TO_N8N_FILES=true (default) to block access to .n8n and user-defined config files, and disabling high-risk nodes (including the Code node) using NODES_EXCLUDE if workflow editors are not fully trusted.

Weakness: CWE-749 (Exposed Dangerous Method or Function), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-68697?

2 open source packages ship an affected version, including n8n. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `n8n` | npm | From 1.2.1 | 2.0.0 |
| `n8n` | npm | From 1.2.1 | 2.0.0 |

Products: N8n N8n.

## How do I fix CVE-2025-68697?

Upgrade n8n to 2.0.0 or later.

## Is CVE-2025-68697 being exploited?

There is no known exploitation of CVE-2025-68697 in the wild and no public exploit code.

## Other vulnerabilities in N8n N8n

- [CVE-2025-68613](https://insights.sbomify.com/CVE-2025-68613/): n8n Improper Control of Dynamically-Managed Code Resources (critical 10.0, exploited in the wild)
- [CVE-2026-21877](https://insights.sbomify.com/CVE-2026-21877/): n8n is vulnerable to Remote Code Execution via Arbitrary File Write (critical 10.0)
- [CVE-2026-21858](https://insights.sbomify.com/CVE-2026-21858/): n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling (critical 10.0)
- [CVE-2026-1470](https://insights.sbomify.com/CVE-2026-1470/): n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution (critical 9.9)
- [CVE-2025-68668](https://insights.sbomify.com/CVE-2025-68668/): n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68697 and fix it if it is affected.

What it is: CVE-2025-68697 is a high-severity vulnerability in N8n N8n, published on 26 Dec 2025. 
Exploitation: There is no known exploitation of CVE-2025-68697 in the wild and no public exploit code.

Affected packages and fixed versions:
- n8n (npm): affected from 1.2.1; fixed in 2.0.0
- n8n (npm): affected from 1.2.1; fixed in 2.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68697/ (Markdown: https://insights.sbomify.com/CVE-2025-68697/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68697
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68697
- OSV: https://osv.dev/vulnerability/CVE-2025-68697

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68697/
Summaries are generated and may contain mistakes; the official description above is the record.