Summary
n8n: MySQL v1 Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Disable the MySQL node by adding
n8n-nodes-base.mySqlto theNODES_EXCLUDEenvironment variable, or audit and restrict access to workflows using the MySQL v1 node with theexecuteQueryoperation. - Ensure that webhook endpoints used in workflows containing MySQL v1
executeQuerynodes with expression interpolation require authentication. - Migrate affected workflows to use the MySQL v2 node, which uses parameterized queries.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Impact
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.
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-59257? CVE-2026-59257 is a medium-severity SQL injection vulnerability in n8n (npm), affecting versions < 1.123.61. It is fixed in 1.123.61, 2.28.1, 2.27.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of n8n are affected by CVE-2026-59257? n8n (npm) versions < 1.123.61 is affected.
- Is there a fix for CVE-2026-59257? Yes. CVE-2026-59257 is fixed in 1.123.61, 2.28.1, 2.27.4. Upgrade to this version or later.
- Is CVE-2026-59257 exploitable, and should I be worried? Whether CVE-2026-59257 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-59257 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-59257?
- Upgrade
n8nto 1.123.61 or later - Upgrade
n8nto 2.28.1 or later - Upgrade
n8nto 2.27.4 or later
- Upgrade