# CVE-2025-57749: n8n has a symlink traversal vulnerability in "Read/Write File" node allows access to restricted files

> Attackers can bypass directory restrictions in the Read/Write File node via symlinks to read or write restricted files.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2025
- **Updated:** 21 Aug 2025
- **Also known as:** GHSA-ggjm-f3g4-rwmm

## What is CVE-2025-57749?

CVE-2025-57749 is a medium-severity path traversal vulnerability in N8n N8n, published on 20 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

n8n is a workflow automation platform. Before 1.106.0, a symlink traversal vulnerability was discovered in the Read/Write File node in n8n. While the node attempts to restrict access to sensitive directories and files, it does not properly account for symbolic links (symlinks). An attacker with the ability to create symlinks—such as by using the Execute Command node—could exploit this to bypass the intended directory restrictions and read from or write to otherwise inaccessible paths. Users of n8n.cloud are not impacted. Affected users should update to version 1.106.0 or later.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `n8n` | npm | All versions | 1.106.0 |
| `n8n` | npm | All versions | 1.106.0 |

Products: N8n N8n.

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

Upgrade n8n to 1.106.0 or later.

## Is CVE-2025-57749 being exploited?

There is no known exploitation of CVE-2025-57749 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-57749 and fix it if it is affected.

What it is: CVE-2025-57749 is a medium-severity path traversal vulnerability in N8n N8n, published on 20 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-57749 in the wild and no public exploit code.

Affected packages and fixed versions:
- n8n (npm): affected all versions; fixed in 1.106.0
- n8n (npm): affected all versions; fixed in 1.106.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-57749/ (Markdown: https://insights.sbomify.com/CVE-2025-57749/index.md)
```

## Sources

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

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