| Package | Affected versions | Patched versions |
|---|---|---|
| n8n | = 2.28.0≥ 2.0.0, < 2.27.4< 1.123.61 | 2.27.41.123.61 |
| n8n | ≥ 2.0.0-rc.0, < 2.27.4≥ 2.28.0, < 2.28.1< 1.123.61 | 2.27.42.28.11.123.61 |
The legacy MySQL v1 node's executeQuery operation substitutes evaluated {{ ... }} expression values directly into the raw SQL string without parameterization. If a workflow uses this operation with expression-sourced values in the query and is connected to an externally-reachable trigger (such as a Webhook node), attacker-controlled input reaching those expressions results in SQL injection.
Successful exploitation allows arbitrary SQL execution with the configured MySQL credentials' privileges, enabling unauthorized disclosure, modification, or deletion of data in the downstream database. MySQL v2 node is not affected.
This issue can affect only instances running workflows that use the MySQL v1 node with executeQuery operations.
The issue has been fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
n8n-nodes-base.mySql to the NODES_EXCLUDE environment variable, or audit and restrict access to workflows using the MySQL v1 node with the executeQuery operation.executeQuery nodes with expression interpolation require authentication.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free