n8n's Improper File Access Controls Allow Arbitrary File Read by Authenticated Users
CriticalCVE-2026-25052 · Published Feb 4, 2026 · updated Feb 5, 2026
## Impact A vulnerability in the file access controls allows authenticated users with permission to create or modify workflows to read sensitive files from the n8n host system. This can be exploited to obtain critical configuration data and user credentials, leading to complete account takeover of any user on the instance. ## Patches The issue has been fixed in n8n version 1.123.18 and 2.5.0. 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: - Limit workflow creation and editing permissions to fully trusted users only. - Restrict access to nodes that interact with the file system, particularly the "Read/Write Files from Disk" and "Git" nodes. 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 backward com...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | >= 2.0.0, < 2.5.0 | 2.5.0 |
| < 1.123.18 | 1.123.18 |
Details and references
## Impact A vulnerability in the file access controls allows authenticated users with permission to create or modify workflows to read sensitive files from the n8n host system. This can be exploited to obtain critical configuration data and user credentials, leading to complete account takeover of any user on the instance. ## Patches The issue has been fixed in n8n version 1.123.18 and 2.5.0. 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: - Limit workflow creation and editing permissions to fully trusted users only. - Restrict access to nodes that interact with the file system, particularly the "Read/Write Files from Disk" and "Git" nodes. 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 backward compatibility. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CVSS 4.0
- CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-367
- Also known as
- CVE-2026-25052
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Feb 4 | n8n's domain allowlist bypass enables credential exfiltration MediumFeb 4 | Medium | 1.121.0 |
| Feb 4 | n8n has a Python sandbox escapeCritical9.9Feb 4 | Critical9.9 | 2.4.8 |
| Feb 4 | n8n Merge Node has Arbitrary File Write leading to RCECriticalFeb 4 | Critical | 1.118.0+1 more |
| Feb 4 | n8n Vulnerable to Arbitrary File Write on Remote Systems via SSH NodeHighFeb 4 | High | 1.123.12+1 more |
| Feb 4 | n8n Has Stored Cross-site Scripting via Markdown Rendering in Workflow UIHighFeb 4 | High | 1.123.9+1 more |
| Feb 4 | n8n has OS Command Injection in Git NodeCriticalFeb 4 | Critical | 1.123.10+1 more |