CVE-2026-77080 in n8n
Summary
by MITRE • 08/20/2026
n8n before 1.123.69, 2.x before 2.33.4, and 2.34.x before 2.34.1 contain an arbitrary file read and write vulnerability in the Snowflake node, which passes free-form Execute Query input, including client-side commands, directly to the Snowflake SDK without applying n8n's file-access restrictions. An authenticated user with usable Snowflake credentials can upload a local file from the n8n host or overwrite an existing file with a staged one.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 08/20/2026
The vulnerability identified in versions of n8n prior to 1.123.69, 2.x before 2.33.4, and 2.34.x before 2.34.1 represents a critical security flaw within the Snowflake integration node. This issue stems from an improper restriction on file system access, specifically classified under CWE-22 as Improper Limitation of a Pathname to a Restricted Directory, or more broadly as CWE-98 in contexts where input control leads to unintended side effects like arbitrary write operations. The core technical flaw arises because the Snowflake node accepts free-form Execute Query inputs from users and passes them directly to the underlying Snowflake SDK without enforcing n8n's standard file-access restrictions. This architectural oversight allows an attacker who has authenticated access to the workflow engine and possesses valid credentials for a connected Snowflake instance to bypass intended security boundaries, effectively turning database query capabilities into mechanisms for arbitrary file system interaction on the host machine running n8n.
From an operational perspective, this vulnerability enables two distinct but related attack vectors: arbitrary file read and arbitrary file write. An authenticated user can exploit the Execute Query functionality to issue commands that instruct the Snowflake client library to access local files on the server hosting the n8n instance. This capability allows for the exfiltration of sensitive data stored locally, such as configuration files containing database credentials, private keys, or other secrets managed by the workflow automation platform. Conversely, the vulnerability also permits arbitrary file writes, allowing an attacker to overwrite existing system files with staged content. This write capability significantly escalates the risk profile from simple information disclosure to potential remote code execution or service disruption, depending on which files are targeted and their permissions within the host operating environment.
The impact of this flaw is severe because it bypasses the isolation layers typically provided by workflow automation platforms. By leveraging valid Snowflake credentials, an attacker does not need to compromise the n8n application logic itself but rather exploits the trust relationship between the node and its underlying SDK. This aligns with ATT&CK techniques such as T1005 (Data from Local System) for reading files and T1222 (File and Directory Permissions Modification) or T1074 (Data Staged) if used to prepare further attacks like lateral movement or persistence mechanisms through file manipulation. The ability to read arbitrary files can lead to credential harvesting, while the write capability could be used to modify application binaries, configuration scripts, or log files to cover tracks or disrupt operations.
Mitigation strategies must prioritize immediate version upgrades and strict input validation. Organizations running affected versions of n8n should upgrade immediately to 1.123.69, 2.33.4, or 2.34.1 where these file-access restrictions have been properly enforced within the Snowflake node implementation. In addition to patching, administrators should review access controls for workflow nodes that interact with external services capable of executing system-level commands. Implementing least-privilege principles for service accounts and ensuring that n8n runs under a restricted user account with minimal filesystem permissions can further reduce the blast radius if such vulnerabilities are present or discovered in other integrations. Regular auditing of node configurations and input sanitization practices is essential to maintain security integrity across automated workflows.