CVE-2026-25052: n8n · Time-of-check Time-of-use (TOCTOU) Race Condition
Affects n8nSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical : upgrade to 2.5.0 or 1.123.18 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.0, 1.123.18
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade n8n and n8n-io/n8n to 2.5.0 or 1.123.18.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n8n-ion8n | Affected
| Fixed in
|
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately upgrade all n8n instances to versions 1.123.18 or 2.5.0 or later, where the vulnerability is patched. 2. Restrict workflow creation and modification permissions strictly to trusted administrators to reduce the number of users who can exploit the vulnerability. 3. Implement robust monitoring and alerting for unusual file access patterns or privilege escalations within n8n environments. 4. Employ network segmentation and access controls to limit exposure of n8n hosts to only necessary users and systems. 5. Regularly audit workflow configurations and user permissions to detect unauthorized changes. 6. Use host-based intrusion detection systems to identify attempts to access sensitive files. 7. Educate administrators and users about the risks of granting workflow modification rights and enforce least privilege principles. 8. Maintain up-to-date backups of critical configuration and workflow data to enable recovery in case of compromise. 9. Consider deploying n8n instances in isolated environments or containers with strict file system permissions to limit impact of potential exploitation. 10. Follow vendor advisories and subscribe to security mailing lists for timely updates on this and related vulnerabilities.
Description
CVE-2026-25052 is a critical TOCTOU race condition vulnerability in the n8n workflow automation platform prior to versions 1.123.18 and 2.5.0. Authenticated users with workflow creation or modification permissions can exploit this flaw to bypass file access controls and read sensitive files on the host system. This exposure can lead to disclosure of critical configuration data and user credentials, enabling complete account takeover of any user on the affected instance. The vulnerability requires low privileges but no user interaction and can be exploited remotely. Although no known exploits are reported in the wild yet, the high CVSS score of 9.4 reflects its severe impact on confidentiality, integrity, and availability.