CVE-2026-42229: n8n: SQL Injection in SeaTable Node
Impact A flaw in the SeaTable node's row:search and row:get operations allowed user-controlled input to be concatenated directly into SQL query strings without escaping or parameterization. In workflows where external user input is passed via expressions into the SeaTable node's search or row retrieval parameters, an attacker could manipulate the constructed query to retrieve unintended rows from the connected SeaTable base, bypassing row-level filtering logic implemented in the workflow.
Exploitation requires a specific workflow configuration: - The SeaTable node must be used with user-controlled input passed via expressions (e.g., from a form or webhook) into the searchTerm or rowId parameters.
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. - Disable the SeaTable node by adding n8n-nodes-base.seaTable to the NODESEXCLUDE environment variable. - Avoid passing unvalidated external user input into SeaTable node search or row retrieval parameters via expressions.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
n8n is an open source workflow automation platform. Prior to versions 1.123.32, 2.17.4, and 2.18.1, a flaw in the SeaTable node's row:search and row:get operations allowed user-controlled input to be concatenated directly into SQL query strings without escaping or parameterization. In workflows where external user input is passed via expressions into the SeaTable node's search or row retrieval parameters, an attacker could manipulate the constructed query to retrieve unintended rows from the connected SeaTable base, bypassing row-level filtering logic implemented in the workflow. This issue has been patched in versions 1.123.32, 2.17.4, and 2.18.1.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-42229?
CVE-2026-42229 is classified as a high severity vulnerability due to the potential for SQL injection.
How do I fix CVE-2026-42229?
To fix CVE-2026-42229, upgrade to n8n version 2.17.4, 2.18.1, or 1.123.32 as these versions contain the necessary security patches.
What are the affected versions for CVE-2026-42229?
CVE-2026-42229 affects n8n versions from 2.0.0 to 2.17.4 and from 2.18.0 to 2.18.1 and also all versions below 1.123.32.
What components are impacted by CVE-2026-42229?
CVE-2026-42229 affects the row:search and row:get operations in the SeaTable node of n8n.
Who is responsible for addressing CVE-2026-42229?
The n8n development team is responsible for addressing CVE-2026-42229 in subsequent releases.