n8n: Snowflake Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation
MediumCVE-2026-72750 · Published Jul 22, 2026 · updated Aug 12, 2026
## Impact The n8n Snowflake node's Execute Query operation interpolated expression values directly into the SQL string, making queries built with untrusted data susceptible to SQL injection. Exploitation requires that a workflow author has already embedded untrusted expression data directly in a raw SQL query. ## Patches The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability. The fix introduces an optional "Query Parameters" field that allows values to be bound via positional placeholders rather than interpolated into the query string. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict workflow creation and editing permissions to fully trusted users only. - Audit existing workflows that use the Snowflake `executeQuery` operation and ensure no expression resolving to externally-controlled data is embedded directly in a raw SQL query string. - Restrict network access to any webhook or trigger endpoints that feed data into Snowflake `executeQuery` nodes. These workarounds do not fully remediate...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | < 1.123.67 | 1.123.67 |
| >= 2.32.0, < 2.32.1 | 2.32.1 | |
| >= 2.0.0-rc.0, < 2.31.5 | 2.31.5 |
Details and references
## Impact The n8n Snowflake node's Execute Query operation interpolated expression values directly into the SQL string, making queries built with untrusted data susceptible to SQL injection. Exploitation requires that a workflow author has already embedded untrusted expression data directly in a raw SQL query. ## Patches The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability. The fix introduces an optional "Query Parameters" field that allows values to be bound via positional placeholders rather than interpolated into the query string. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict workflow creation and editing permissions to fully trusted users only. - Audit existing workflows that use the Snowflake `executeQuery` operation and ensure no expression resolving to externally-controlled data is embedded directly in a raw SQL query string. - Restrict network access to any webhook or trigger endpoints that feed data into Snowflake `executeQuery` nodes. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CVSS 4.0
- CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-89
- Also known as
- CVE-2026-72750
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Jul 22 | n8n: SQL injection MediumJul 22 | Medium | 1.123.67+2 more |
| Jul 22 | n8n: Cross-Tenant Module-Cache Poisoning in the JS Task RunnerMediumJul 22 | Medium | 1.123.67+2 more |
| Jul 22 | n8n: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution DataMediumJul 22 | Medium | 1.123.64+2 more |
| Jul 22 | n8n: Unauthenticated Endpoint Allows Cancellation of Any User's Active Test WebhookMediumJul 22 | Medium | 2.27.4 |
| Jul 22 | n8n: GraphQL Node Bypasses "Allowed HTTP Request Domains" RestrictionMediumJul 22 | Medium | 1.123.64+2 more |
| Jul 22 | n8n: improper authorizationMediumJul 22 | Medium | 2.29.8+1 more |