# CVE-2026-42237: n8n SQL Injection — Fixed in 1.123.32

📦 npm

Not in CISA KEV

# CVE-2026-42237 — n8n

CVE-2026-42237 is a SQL Injection vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

n8n: SQL Injection in Snowflake and MySQL Nodes

Also known as[GHSA-hp3c-vfpm-q4f7](/vulnerability/GHSA-hp3c-vfpm-q4f7)

Published

May 4, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-42237.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

0.00%0.31%0.63%0.94%0.0%0.3%Jun 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

36other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`n8n`npm

151Kdownloads / week

## Description

### Impact

The 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.

Exploitation requires a specific workflow configuration:

-   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.

Successful exploitation could allow data exfiltration, modification, or deletion on the downstream database.

### Patches

The 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.

### Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

-   Limit workflow creation and editing permissions to fully trusted users only.
-   Migrate workflows from the legacy MySQL v1 node to the MySQL v2 node, which already implements identifier escaping.
-   Disable the Snowflake node by adding `n8n-nodes-base.snowflake` to the `NODES_EXCLUDE` environment variable.
-   Avoid passing unvalidated external user input into table name, column name, or update key fields via expressions in the affected nodes.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

## Affected Packages

3 total 3 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`n8n` 

all versions

1.123.32`npm install n8n@1.123.32`

📦npm

`n8n` 

≥ 2.18.0&&< 2.18.1

2.18.1`npm install n8n@2.18.1`

📦npm

`n8n` 

≥ 2.0.0&&< 2.17.4

2.17.4`npm install n8n@2.17.4`

## Affected Products

1 product · 3 configurations

Application

`n8n`n8n

≥ 2.17.0 && < 2.17.4

1 version

2.18.0

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update n8n to 1.123.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42237 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
    

## Frequently Asked Questions

\## Impact The 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. Exploitation requires a specific workflow configuration: - 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

O3 Security · Impact-Aware SCA

### Is CVE-2026-42237 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)