CVE-2026-42229
SQL Injection in n8n SeaTable Node
Publication date: 2026-05-04
Last updated on: 2026-05-06
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| n8n | n8n | to 1.123.32 (exc) |
| n8n | n8n | 2.18.0 |
| n8n | n8n | From 2.17.0 (inc) to 2.17.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the n8n workflow automation platform, specifically in the SeaTable node's row:search and row:get operations. Before certain fixed versions, user-controlled input was directly concatenated into SQL query strings without proper escaping or parameterization. This allowed an attacker to manipulate the SQL queries by injecting malicious input, potentially retrieving unintended rows from the connected SeaTable base and bypassing row-level filtering logic.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to bypass row-level filtering in workflows using the SeaTable node, leading to unauthorized access to data rows that should be restricted. This could result in exposure of sensitive or confidential information stored in the SeaTable base, potentially compromising data integrity and confidentiality.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the n8n platform to one of the patched versions: 1.123.32, 2.17.4, or 2.18.1.
Avoid passing external user input directly into the SeaTable node's row:search and row:get operations without proper escaping or parameterization.