dbcve.org
N8nApplication

CVE-2026-42237

HIGH · 8.8 CVSS v3.1 Published 2026-05-04
Fix available
A fix is available. Upgrade to 1.123.32 / 2.17.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
n8n is an open source workflow automation platform. Prior to versions 1.123.32, 2.17.4, and 2.18.1, the fix for 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. This issue has been patched in versions 1.123.32, 2.17.4, and 2.18.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

n8n workflow automation platform versions prior to 1.123.32, 2.17.4, and 2.18.1 contain SQL injection vulnerabilities in the Snowflake node and 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 proper identifier escaping, allowing attackers to inject malicious SQL via these parameters against the connected database.

MitigationUpgrade n8n to version 1.123.32, 2.17.4, or 2.18.1 or later to receive the patch that adds proper SQL identifier escaping to the Snowflake and MySQL v1 nodes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 1.123.32>= 2.17.0, < 2.17.4= 2.18.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check n8n version
    Access the n8n UI and navigate to Settings > About, or query the API endpoint /rest/settings, or run 'n8n --version' from the command line if self-hosted
    Affected if The installed version is below 1.123.32, or between 2.17.0 and 2.17.3 inclusive, or exactly 2.18.0
  2. Identify Snowflake node usage
    Open the n8n UI, go to Workflows, and search each workflow for nodes of type 'n8n-nodes-base.snowflake' or search your workflow JSON exports for 'snowflake' in the node type field
    Affected if Any workflow contains a Snowflake node that uses dynamic table names, column names, or update keys from workflow data or expressions
  3. Identify MySQL v1 node usage
    Open the n8n UI and search workflows for nodes of type 'n8n-nodes-base.mySql' (the legacy v1 node, not the newer mysql2 node), or check workflow JSON exports for this node type
    Affected if Any workflow contains a MySQL v1 node that uses dynamic table names, column names, or update keys from workflow data or expressions
  4. Review node configuration for dynamic parameters
    For each Snowflake or MySQL v1 node found, open the node settings and inspect the Table, Columns, or Update Key fields. Check if these fields contain expressions referencing workflow data, webhook inputs, or other dynamic sources rather than static values
    Affected if The Snowflake or MySQL v1 node has Table, Column, or Update Key parameters configured with expressions that could be influenced by external input

You are affected if your n8n installation version is vulnerable AND you have active workflows using Snowflake or MySQL v1 nodes with dynamic identifiers in query parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.123.32 / 2.17.4 or later
Fixed in 1.123.322.17.4
Interim mitigation

Upgrade n8n to version 1.123.32, 2.17.4, or 2.18.1 or later to receive the patch that adds proper SQL identifier escaping to the Snowflake and MySQL v1 nodes.

Recommended fix High confidence

1.123.32 (for 1.x) or 2.17.4/2.18.1 (for 2.x)

  1. 1. Identify the current n8n version by checking the running instance or package.json
  2. 2. If using version 1.x branch: upgrade to version 1.123.32
  3. 3. If using version 2.x branch: upgrade to version 2.17.4 (if on 2.17.x) or 2.18.1 (if on 2.18.x)
  4. 4. Before upgrading, backup the n8n database and configuration files
  5. 5. Perform the upgrade using the standard upgrade method for your deployment (npm, Docker, or binary)
  6. 6. Restart the n8n service
  7. 7. Verify the Snowflake node and MySQL v1 node work correctly after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42237 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42237 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data