CVE-2026-72750 Overview
CVE-2026-72750 is a SQL injection vulnerability in n8n, the workflow automation platform. The flaw resides in the Snowflake node's Execute Query operation, which interpolates expression values directly into the SQL string. When a workflow author embeds untrusted, externally-controlled expression data in a raw SQL query, that data is not parameterized. An attacker who controls the expression input can inject arbitrary SQL statements into the query executed against Snowflake.
The issue is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command. It affects n8n versions prior to 1.123.67, 2.31.5, and 2.32.1.
Critical Impact
Attackers who influence workflow expression data can execute arbitrary SQL against connected Snowflake databases, compromising data confidentiality and integrity in downstream systems.
Affected Products
- n8n versions before 1.123.67
- n8n versions before 2.31.5
- n8n versions before 2.32.1
Discovery Timeline
- 2026-08-11 - CVE-2026-72750 published to NVD
- 2026-08-11 - Last updated in NVD database
Technical Details for CVE-2026-72750
Vulnerability Analysis
n8n allows workflow authors to compose SQL queries executed against Snowflake through the Execute Query operation of the Snowflake node. The node accepts expression syntax that references upstream data, environment variables, or webhook payloads. Before the patched releases, the node concatenated these expression values directly into the raw SQL string sent to Snowflake.
When expression inputs originate from untrusted sources such as HTTP webhook triggers, form nodes, or external APIs, an attacker can inject SQL fragments that alter query semantics. Injected payloads can read arbitrary tables, modify records, or invoke Snowflake-supported functions within the privileges of the configured Snowflake account.
Root Cause
The root cause is the absence of parameterized query binding in the Snowflake node's Execute Query path. Expression values were serialized into the SQL text as string interpolation rather than passed as bound parameters. Any character with SQL semantic meaning, such as single quotes, semicolons, or comment markers, passes through unescaped and is parsed by Snowflake.
Attack Vector
Exploitation requires a workflow that both consumes externally-controlled input and forwards that input into a Snowflake Execute Query node without sanitization. Common exposure patterns include webhook-triggered workflows, chatbots writing user prompts into queries, and integrations that map third-party API responses to query filters. The attacker does not need direct access to n8n; they only need to reach an input source consumed by a vulnerable workflow.
See the GitHub Security Advisory GHSA-652q-gvq3-74qv and the VulnCheck Advisory on SQL Injection for additional technical detail.
Detection Methods for CVE-2026-72750
Indicators of Compromise
- Snowflake query history entries containing unexpected UNION SELECT, stacked statements separated by ;, or SQL comment sequences such as -- and /* originating from n8n service accounts.
- Workflow execution logs in n8n showing Snowflake node inputs with characters typical of SQL injection payloads within expression fields.
- Anomalous Snowflake result set sizes or query durations tied to workflows that normally return bounded data.
Detection Strategies
- Audit all n8n workflows using the Snowflake node and identify those whose Execute Query operation references expressions bound to webhook, form, or external API data.
- Enable Snowflake query tagging on n8n connections and alert on queries containing injection-indicative patterns.
- Correlate n8n execution logs with Snowflake QUERY_HISTORY to identify SQL text that deviates from the templated query for a given workflow.
Monitoring Recommendations
- Forward n8n execution logs and Snowflake ACCESS_HISTORY to a centralized SIEM for continuous monitoring.
- Alert on n8n service account activity that reads tables outside the expected workflow scope.
- Track deployed n8n version across environments and flag hosts running versions below the patched releases.
How to Mitigate CVE-2026-72750
Immediate Actions Required
- Upgrade n8n to 1.123.67, 2.31.5, 2.32.1, or later depending on your release track.
- Rotate Snowflake credentials used by n8n if untrusted input reached the Snowflake node before patching.
- Review Snowflake query history for the affected time window and confirm no unauthorized data access occurred.
Patch Information
The maintainers fixed the issue by adding an optional Query Parameters field to the Snowflake node's Execute Query operation. Workflow authors can now bind values via positional placeholders instead of interpolating expression values into the raw SQL string. Refer to GHSA-652q-gvq3-74qv for release details.
Workarounds
- Refactor Snowflake Execute Query nodes to use the new Query Parameters field with positional placeholders for any value derived from expressions.
- Restrict the Snowflake role assigned to n8n to the minimum tables and operations required by the workflow.
- Validate and sanitize webhook or form inputs upstream of any Snowflake node until refactoring is complete.
# Upgrade n8n via npm to a patched release
npm install -g n8n@1.123.67
# Or pull the patched Docker image
docker pull n8nio/n8n:2.32.1
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
