Alex Joseph
CVE Details
- Product: n8n
- CVE ID: CVE-2026-72750
- Published: August 11, 2026
- Severity: HIGH (CVSS score 8.8)
- Status: Analyzed
Affected Products
The SQL injection vulnerability affects several versions of n8n, specifically those prior to the patched releases. Both community and enterprise editions running on Node.js are impacted.
Affected versions include:
- n8n versions before 1.123.67
- n8n versions before 2.31.5
- n8n versions before 2.32.1
- Specifically, n8n 2.32.0 (community and enterprise editions) is also affected.
Current Status
This vulnerability has been officially analyzed, and patches have been released to address the issue. Users are strongly advised to upgrade their n8n installations to a secure version as soon as possible.
Severity Level
The Common Vulnerability Scoring System (CVSS) assigns this vulnerability a score of 8.8, classifying it as **HIGH** severity. This indicates that the vulnerability is easily exploitable and could lead to significant data breaches or system compromise. While a GitHub advisory for this specific issue classified it as “Moderate” with a CVSS v4 score of 5.3, the CVE entry reflects a “HIGH” severity, which is generally a more comprehensive assessment. The risk primarily arises when workflow authors mistakenly embed untrusted, externally-controlled data directly into unparameterized SQL queries within the Snowflake node.
Possible Solutions
The developers of n8n have released patches to fix this SQL injection vulnerability.
Patched Versions:
Users should upgrade their n8n instance to one of the following versions or later:
- n8n version 1.123.67 or greater
- n8n version 2.31.5 or greater
- n8n version 2.32.1 or greater
The fix introduces a new, optional ‘Query Parameters’ field within the Snowflake node’s ‘Execute Query’ operation. This field allows values to be safely bound using positional placeholders, preventing direct interpolation into the SQL string and thus mitigating the SQL injection risk.
Temporary Workarounds:
If an immediate upgrade is not feasible, consider these temporary mitigation steps:
- Restrict Workflow Permissions: Limit who can create or edit workflows to only highly trusted users.
- Audit Workflows: Carefully review existing workflows that utilize the Snowflake `executeQuery` operation. Ensure that no data controlled by external, untrusted sources is directly embedded into raw SQL query strings. Always use parameterized queries for dynamic data.
- Network Access Control: Restrict network access to any webhook or trigger endpoints that feed data into Snowflake `executeQuery` nodes.
It’s important to remember that these workarounds are only temporary measures and do not fully eliminate the risk. A full upgrade to a patched version is the most effective solution.
References
https://github.com/n8n-io/n8n/security/advisories/GHSA-652q-gvq3-74qv
https://www.vulncheck.com/advisories/n8n-before-sql-injection-via-executequery-operation
