CVE-2026-42237: N8n SQL Injection Vulnerability
MODERATECVE-2026-42237 is a MODERATE (CVSS 8.2) sql injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting N8n libraries in the npm ecosystem. The issue involves n8n has sql injection in snowflake and mysql nodes. Remediation is available by upgrading affected packages to version 1.123.32, 2.18.1, 2.17.4.
CVE-2026-42237 at a Glance
Security Impact
CVSS: 8.2
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N).
How to Fix CVE-2026-42237
To remediate this vulnerability, upgrade all affected N8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install n8n@1.123.32npm install n8n@2.18.1npm install n8n@2.17.4Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls n8nHow to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-42237, inspect your project dependencies using npm:
npm ls n8nAnalyze the terminal output to locate any version of N8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.123.32), your application is affected.
Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where 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. In N8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-42237 Affected N8n Versions
3 component(s)References
Frequently Asked Questions
What is CVE-2026-42237?
Which N8n versions are affected?
What version fixes CVE-2026-42237?
Is n8n affected?
What is the CVSS score of CVE-2026-42237?
What CWE is associated with CVE-2026-42237?
How can I check npm dependencies for CVE-2026-42237?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hp3c-vfpm-q4f7",
"modified" : "2026-05-08T01:30:35Z",
"published" : "2026-04-29T21:03:29Z",
"aliases" : [ "CVE-2026-42237" ],
"summary" : "n8n has SQL Injection in Snowflake and MySQL Nodes",
"details" : "## Impact\nThe fix for [GHSA-f3f2-mcxc-pwjx](https://github.com/advisories/GHSA-f3f2-mcxc-pwjx) did not cover the Snowflake node or the legacy MySQL v1 node. Both nodes construct SQL queries by directly interpolating user-controlled table names, column names, and update keys into query strings without identifier escaping, enabling SQL injection against the connected database.\n\nExploitation requires a specific workflow configuration:\n- The Snowflake or MySQL v1 node must be used with user-controlled input passed via expressions (e.g., from a form or webhook) into identifier fields such as table name, column name, or update key.\n\nSuccessful exploitation could allow data exfiltration, modification, or deletion on the downstream database.\n\n## Patches\nThe issue has been fixed in n8n versions 1.123.32, 2.17.4, and 2.18.1. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Limit workflow creation and editing permissions to fully trusted users only.\n- Migrate workflows from the legacy MySQL v1 node to the MySQL v2 node, which already implements identifier escaping.\n- Disable the Snowflake node by adding `n8n-nodes-base.snowflake` to the `NODES_EXCLUDE` environment variable.\n- Avoid passing unvalidated external user input into table name, column name, or update key fields via expressions in the affected nodes.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.123.32"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.18.0"
}, {
"fixed" : "2.18.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0.0"
}, {
"fixed" : "2.17.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-f3f2-mcxc-pwjx"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-hp3c-vfpm-q4f7"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42237"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/n8n-io/n8n"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-89" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-29T21:03:29Z",
"nvd_published_at" : "2026-05-04T19:16:06Z"
}
}