SA-26-007 High

n8n: Prior to versions 1.123.32, 2.17.4, and 2.18.1, a flaw in the SeaTable node's row:search and…

n8n

Severity
High, CVSS 8.8
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Record
CVE-2026-42229
Affects
n8n
Known exploited
Not listed in the CISA Known Exploited Vulnerabilities catalog
Published
Record first published by the source
May 4, 2026
Source last modified
October 26, 2026

Description

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.

Description quoted from the NVD record.

Who is affected

This flaw affects n8n, a tool for automating tasks by linking apps and services into workflows, in versions before 1.123.32, 2.17.4 and 2.18.1. The problem is in the building block that connects workflows to SeaTable, specifically its search and row lookup actions. It matters when a workflow passes input from outside users into those search or lookup settings. In that case, an attacker could change the lookup so it returns rows from the connected SeaTable data that they should not see, getting around any row filtering the workflow sets up. This flaw is rated High.

What to do

  1. The person who installed or runs n8n for your organization should check which version is in use. If an IT provider or vendor runs it for you, send them this advisory and ask when the update will be done.
  2. Update n8n to version 1.123.32, 2.17.4 or 2.18.1, whichever matches the version series you use, or to a later release.
  3. Ask the person who builds your workflows to find any workflow that passes input from outside users into the SeaTable building block's search or row lookup actions, so you know where the risk lies until the update is done.
  4. After updating, check that n8n reports one of the fixed versions or a later one.

Analysis written from the source record as of October 26, 2026 and reviewed before publishing.

Sources

MORE ADVISORIES

See all