Summary
Workarounds
Until the patch is applied:
- Disable or restrict access to the
Execute Commandnode and any other nodes that allow arbitrary file system access. - Avoid using the
Read/Write Filenode on untrusted paths or inputs that could be manipulated via symlinks.
Impact
A symlink traversal vulnerability was discovered in the Read/Write File node in n8n. While the node attempts to restrict access to sensitive directories and files, it does not properly account for symbolic links (symlinks). An attacker with the ability to create symlinks, such as by using the Execute Command node, could exploit this to bypass the intended directory restrictions and read from or write to otherwise inaccessible paths. Users of n8n.cloud are not impacted.
CVE-2025-57749 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.106.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Affected users should update to version 1.106.0 or later.
Frequently Asked Questions
- What is CVE-2025-57749? CVE-2025-57749 is a medium-severity security vulnerability in n8n (npm), affecting versions < 1.106.0. It is fixed in 1.106.0.
- How severe is CVE-2025-57749? CVE-2025-57749 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of n8n are affected by CVE-2025-57749? n8n (npm) versions < 1.106.0 is affected.
- Is there a fix for CVE-2025-57749? Yes. CVE-2025-57749 is fixed in 1.106.0. Upgrade to this version or later.
- Is CVE-2025-57749 exploitable, and should I be worried? Whether CVE-2025-57749 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-57749 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-57749? Upgrade
n8nto 1.106.0 or later.