CVE-2025-57749 is a symlink traversal vulnerability affecting versions of the n8n workflow automation platform prior to 1.106.0. The vulnerability resides in the Read/Write File node, which is designed to restrict access to sensitive directories and files. However, the node fails to properly handle symbolic links (symlinks), allowing an attacker who can create symlinks—such as through the Execute Command node—to bypass these directory restrictions. By exploiting this flaw, an attacker can read from or write to files and directories that should be inaccessible, potentially exposing sensitive data or modifying critical files. The vulnerability is classified under CWE-59 (Improper Link Resolution Before File Access), indicating a failure to securely resolve symlinks before file operations. The CVSS v3.1 base score is 6.5 (medium severity), with the vector indicating network attack vector (AV:N), low attack complexity (AC:L), requiring privileges (PR:L), no user interaction (UI:N), unchanged scope (S:U), high confidentiality impact (C:H), no integrity impact (I:N), and no availability impact (A:N). Notably, users of the n8n.cloud managed service are not affected, as this vulnerability pertains to self-hosted instances. No known exploits are currently reported in the wild, but the vulnerability poses a significant risk due to the potential for unauthorized file access and modification. The recommended remediation is to upgrade to n8n version 1.106.0 or later, where the issue has been fixed.

For European organizations using self-hosted n8n instances, this vulnerability could lead to unauthorized disclosure of sensitive information, including configuration files, credentials, or proprietary data, due to the high confidentiality impact. Although the vulnerability does not affect integrity or availability directly, unauthorized write access could enable attackers to modify files, potentially leading to further compromise or persistence. Given that n8n is often used to automate workflows involving business-critical processes, exploitation could disrupt operations indirectly or facilitate lateral movement within networks. The requirement for attacker privileges to create symlinks limits the attack surface to insiders or attackers who have already gained limited access, but the lack of required user interaction and low attack complexity means exploitation could be automated once initial access is obtained. European organizations in sectors such as finance, healthcare, manufacturing, and government that rely on n8n for automation could face data breaches or compliance violations under GDPR if sensitive personal data is exposed. The impact is heightened by the potential difficulty in detecting such symlink traversal attacks, as they exploit legitimate workflow nodes.

Beyond the essential step of upgrading to n8n version 1.106.0 or later, European organizations should implement strict access controls on who can create or execute workflows, especially those involving the Execute Command and Read/Write File nodes. Restrict permissions to trusted administrators and enforce the principle of least privilege to minimize the risk of symlink creation by unauthorized users. Employ runtime monitoring and file integrity monitoring to detect unusual file access patterns or modifications indicative of exploitation attempts. Network segmentation can limit exposure of n8n instances to trusted internal networks only. Additionally, conduct regular audits of workflow configurations to identify potentially dangerous nodes or scripts that could be abused. Organizations should also consider deploying endpoint detection and response (EDR) solutions capable of detecting suspicious command executions or symlink manipulations. Finally, maintain up-to-date backups of critical data to recover from potential unauthorized modifications.