CVE-2026-42229 Overview
CVE-2026-42229 is a SQL injection vulnerability in n8n, an open source workflow automation platform. The flaw exists in the SeaTable node's row:search and row:get operations, where user-controlled input is concatenated directly into SQL query strings without escaping or parameterization [CWE-89]. Workflows that pass external user input through expressions into the SeaTable node's search or row retrieval parameters are exposed. An attacker can manipulate the constructed query to retrieve unintended rows from the connected SeaTable base, bypassing row-level filtering logic implemented in the workflow. The issue affects n8n versions prior to 1.123.32, 2.17.4, and 2.18.1.
Critical Impact
Authenticated attackers can bypass workflow row-level filtering and exfiltrate unintended SeaTable records through crafted input passed to the SeaTable node.
Affected Products
- n8n versions prior to 1.123.32
- n8n versions 2.0.0 through 2.17.3
- n8n versions 2.18.0
Discovery Timeline
- 2026-05-04 - CVE CVE-2026-42229 published to NVD
- 2026-05-06 - Last updated in NVD database
Technical Details for CVE-2026-42229
Vulnerability Analysis
The vulnerability resides in the SeaTable integration node shipped with n8n. The node exposes row:search and row:get operations that build SQL statements to query a connected SeaTable base. Instead of using parameterized queries or escaping user input, the node concatenates expression-evaluated values directly into the query string. This allows an attacker who can influence those expression inputs to inject arbitrary SQL fragments.
The attack does not require code execution on the n8n host. It abuses the SeaTable query interface to read data the workflow author intended to gate behind filtering logic. The CWE-89 classification confirms improper neutralization of special elements used in an SQL command.
Root Cause
The SeaTable node assembles SQL queries through string concatenation using values supplied via n8n expressions. These expressions can resolve to data from prior nodes, including data sourced from webhook payloads, form submissions, or other external triggers. Because the values bypass parameterization, characters such as quotes and SQL clauses are interpreted as part of the query syntax rather than as literal data.
Attack Vector
Exploitation requires a workflow where untrusted input flows into the SeaTable node's search or row parameters. An attacker triggers the workflow with crafted input that closes the original predicate and appends a clause such as OR 1=1 or a UNION SELECT to alter the query result set. The constructed query then returns rows that the workflow's filter conditions would normally exclude. Because the network attack vector applies, any externally reachable trigger that feeds into the vulnerable node is sufficient. No verified public proof-of-concept code is available at this time. See the n8n GitHub Security Advisory GHSA-mp4j-h6gh-f6mp for vendor technical details.
Detection Methods for CVE-2026-42229
Indicators of Compromise
- SeaTable query logs containing unexpected SQL syntax such as stacked predicates, UNION, comment markers (--, /*), or unbalanced quotes originating from n8n workflow executions.
- n8n execution history showing SeaTable node outputs that return more rows than the workflow's filter logic should permit.
- Webhook or form trigger payloads containing single quotes, SQL keywords, or boolean tautologies routed into SeaTable operations.
Detection Strategies
- Audit all n8n workflows that use the SeaTable node and identify operations of type row:search or row:get whose parameters reference upstream expression data.
- Inspect SeaTable server-side query logs for malformed or anomalous SQL emitted by the n8n integration user.
- Compare row counts and field values returned by SeaTable nodes against the workflow's documented filter intent to surface bypassed restrictions.
Monitoring Recommendations
- Forward n8n execution logs and SeaTable access logs to a centralized analytics platform for correlation of trigger inputs with downstream query outputs.
- Alert on SeaTable queries originating from the n8n service account that contain SQL metacharacters not present in legitimate workflow templates.
- Track the running n8n version across all instances and flag deployments below 1.123.32, 2.17.4, or 2.18.1.
How to Mitigate CVE-2026-42229
Immediate Actions Required
- Upgrade n8n to version 1.123.32, 2.17.4, or 2.18.1 depending on the deployed release branch.
- Inventory workflows using the SeaTable node and identify any that pass externally sourced data into row:search or row:get operations.
- Rotate SeaTable API tokens used by n8n if logs indicate possible exploitation prior to patching.
Patch Information
The vendor patched the issue in n8n versions 1.123.32, 2.17.4, and 2.18.1. The fix replaces unsafe string concatenation in the SeaTable node with proper escaping or parameterization of user-supplied values. Refer to the n8n GitHub Security Advisory GHSA-mp4j-h6gh-f6mp for the official advisory.
Workarounds
- Sanitize and validate all expression inputs feeding the SeaTable node, rejecting characters such as single quotes and SQL keywords before they reach the node parameters.
- Restrict workflows containing SeaTable row:search or row:get operations so they cannot be invoked by untrusted external triggers until patched.
- Apply least-privilege scoping to the SeaTable API credentials used by n8n so a successful injection cannot reach bases beyond the intended scope.
# Upgrade n8n via npm to a fixed release
npm install -g n8n@2.18.1
# Or pull the patched Docker image
docker pull n8nio/n8n:2.18.1
docker stop n8n && docker rm n8n
docker run -d --name n8n -p 5678:5678 n8nio/n8n:2.18.1
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
