CVE-2026-25052: n8n Improper File Access Controls Allow Arbitrary File Read by Authenticated Users

Published Feb 4, 2026
·
Updated

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 — 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

Other sources

n8n is an open source workflow automation platform. Prior to versions 1.123.18 and 2.5.0, 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. This issue has been patched in versions 1.123.18 and 2.5.0.

MITRE

Affected Software

5 affected componentsFixes available
npm/n8n<1.123.18, <2.5.0
npm/n8n<1.123.18
1.123.18
npm/n8n>=2.0.0<2.5.0
2.5.0
n8n N8n Node.js<1.123.18
n8n N8n Node.js>=2.0.0<2.5.0

Event History

Feb 4, 2026
CVE Published
via MITRE·04:47 PM
Data Sourced
via MITRE·04:47 PM
DescriptionWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:25 PM
Data Sourced
via GitHub·06:25 PM
DescriptionWeaknessAffected Software
Jun 19, 58090
Event
via FIRST·04:06 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-25052?

CVE-2026-25052 is categorized as a medium severity vulnerability due to the potential for unauthorized access to sensitive files by authenticated users.

2

How do I fix CVE-2026-25052?

To remediate CVE-2026-25052, upgrade to n8n version 1.123.18 or 2.5.0 or later releases.

3

Who is affected by CVE-2026-25052?

CVE-2026-25052 affects authenticated users of n8n who have permission to create or modify workflows.

4

What type of vulnerability is CVE-2026-25052?

CVE-2026-25052 is an improper file access control vulnerability that allows arbitrary file read.

5

Can CVE-2026-25052 lead to data exposure?

Yes, CVE-2026-25052 can lead to data exposure by allowing access to sensitive files on the n8n host system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203