CVE-2026-42237
SQL Injection in n8n Workflow Automation Platform
Publication date: 2026-05-04
Last updated on: 2026-05-06
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| n8n | n8n | to 1.123.32 (exc) |
| n8n | n8n | 2.18.0 |
| n8n | n8n | From 2.17.0 (inc) to 2.17.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows SQL injection through unescaped user-controlled inputs in certain nodes of the n8n workflow automation platform. This could potentially lead to unauthorized access or manipulation of sensitive data stored in connected databases.
Such unauthorized access or data manipulation could impact compliance with data protection standards and regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches.
However, the provided information does not explicitly describe the direct impact on compliance with these standards.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute arbitrary SQL commands on the connected database by injecting malicious SQL code through user-controlled inputs. This can lead to unauthorized data access, data modification, or even deletion, potentially compromising the integrity and confidentiality of the database.
Can you explain this vulnerability to me?
This vulnerability exists in the n8n workflow automation platform prior to versions 1.123.32, 2.17.4, and 2.18.1. Specifically, the Snowflake node and the legacy MySQL v1 node construct SQL queries by directly inserting user-controlled table names, column names, and update keys into query strings without properly escaping identifiers. This improper handling allows an attacker to perform SQL injection attacks against the connected database.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade n8n to one of the patched versions: 1.123.32, 2.17.4, or 2.18.1.
These versions include fixes that properly escape identifiers in SQL queries constructed by the Snowflake node and the legacy MySQL v1 node, preventing SQL injection.