Security Digest · Vulnerability record
CVE-2026-25052: n8n's Improper File Access Controls Allow Arbitrary File Read by Authenticated Users
n8n is an open source workflow automation platform.
CVSS 9.4 Critical EPSS 0.3% · p25
Should you act?
Critical, preconditions apply
Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.3%, percentile 25: FIRST’s model estimates a 0.3% chance of exploitation activity in the next 30 days, higher than 25% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Needs an account (low (any account)). Exposure depends on who can log in.
- Only applies if your dependency tree includes
n8n(npm) >= 2.0.0, < 2.5.0, fixed in 2.5.0;n8n(npm) < 1.123.18, fixed in 1.123.18. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
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
Weakness type: CWE-367.
Product: n8n (npm) · Assigned by: GitHub_M · Published: 2026-02-04
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| npm | n8n | >= 2.0.0, < 2.5.0 | 2.5.0 |
| npm | n8n | < 1.123.18 | 1.123.18 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| n8n-io | n8n | < 1.123.18, < 2.5.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 4.0 | 9.4 Critical | 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 |
| GitHub | 4.0 | 9.4 | 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 |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: none
- Privileges required: low (any account)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 0.33% probability of exploitation activity in the next 30 days; percentile 25.
Timeline
- — CVE record published by GitHub_M
- — GitHub-reviewed advisory GHSA-gfvg-qv54-r4pc published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-gfvg-qv54-r4pc github.com
- CVE.org record CVE-2026-25052 cve.org
- NVD entry CVE-2026-25052 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com