CVE-2026-25052 is a critical flaw (CVSS 9.9) in n8n, the workflow automation platform. A hole in file access controls lets a user who can create or edit workflows read sensitive files from the host, including configuration and credentials. n8n 1.123.18 and 2.5.0 fix it, so upgrade and restrict who can edit workflows.
What's affected
- Affected: n8n before 1.123.18 on 1.x, and before 2.5.0 on 2.x.
- Fixed in: 1.123.18 and 2.5.0.
- Who can trigger it: authenticated users with permission to create or modify workflows.
The advisory says the exposed data can be used to take over any user account on the instance. n8n lists its own severity as 9.4 under CVSS 4.0, while the NVD record shows 9.9 under CVSS 3.1.
How to check if you're exposed
Check the n8n version first, in the interface or from the container tag.
docker ps --format '{{.Image}}' | grep n8n
Then list your users and their roles, and count how many can create or edit workflows. Each of them could read files the n8n process can read. Think about what is on that disk: the configuration, the encryption key, database files and any mounted secrets.
What to do now
- Upgrade to n8n 1.123.18 or later on 1.x, or 2.5.0 or later on 2.x.
- Limit workflow creation and editing to fully trusted users. This is the advisory's workaround.
- Restrict access to nodes that touch the file system, the advisory names the "Read/Write Files from Disk" node and the Git node. n8n's documentation covers how to block nodes globally.
- Treat the workarounds as short term. The advisory says they do not fully remediate the risk.
- If you suspect misuse, rotate the credentials and the encryption key that lived on the host, and force password resets.
Why it matters
The advisory classes this weakness as CWE-367 (Time-of-check Time-of-use Race Condition), a time-of-check time-of-use race condition. That means a check on a file and the later use of that file are not tied together, so the state can change in between and the check no longer protects anything. Race conditions are subtle because they pass casual testing.
For an automation platform, file reads are serious because the host holds the keys to everything the workflows touch. A single read of a configuration file can turn a low level editor account into a full takeover.
Quick check
Is CVE-2026-25052 on the CISA KEV list?
No. The record marks it as not known exploited, and the advisory does not report exploitation.
Does blocking the file nodes fully protect me?
No. The advisory describes the node restrictions as a short term measure and recommends upgrading.
Sources
Last reviewed: 19 October 2026.
