dbcve.org
N8nApplication

CVE-2026-42229

HIGH · 8.8 CVSS v3.1 Published 2026-05-04
Fix available
A fix is available. Upgrade to 1.123.32 / 2.17.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SeaTable node in n8n versions prior to 1.123.32, 2.17.4, and 2.18.1 contains a SQL injection vulnerability in its row:search and row:get operations. User-controlled input passed through expressions is directly concatenated into SQL query strings without escaping or parameterization, allowing attackers to manipulate queries and retrieve unauthorized data from SeaTable bases.

MitigationUpgrade n8n to version 1.123.32, 2.17.4, or 2.18.1. Additionally, audit existing workflows using the SeaTable node to identify and remediate any instances where untrusted input flows into search or retrieval parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 1.123.32>= 2.17.0, < 2.17.4= 2.18.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check n8n version
    Navigate to the n8n UI, go to Settings > About, or run `n8n --version` from the command line to identify the installed version
    Affected if The installed version is less than 1.123.32, or between 2.17.0 and 2.17.4 exclusive, or exactly 2.18.0
  2. Identify workflows using SeaTable node
    In the n8n UI, search for workflows containing the SeaTable integration node, or inspect workflow JSON files for nodes with type containing 'seatable'
    Affected if Any workflow uses the SeaTable node in the affected n8n version
  3. Inspect SeaTable node operations
    Open each workflow using SeaTable and examine the node configuration to identify if 'row:search' or 'row:get' operations are being used
    Affected if The SeaTable node is configured to use row:search or row:get operations
  4. Check for user-controlled input in expressions
    Review the parameters in the row:search or row:get configuration, looking for expression fields that reference workflow input data, webhooks, HTTP request data, or other user-controllable sources
    Affected if Expressions containing potentially untrusted input (such as workflow input, webhook data, or external API responses) are used in search or filter parameters

A user is affected if they run a vulnerable n8n version AND have workflows using the SeaTable node with row:search or row:get operations where user-controlled input flows into query expressions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.123.32 / 2.17.4 or later
Fixed in 1.123.322.17.4
Interim mitigation

Upgrade n8n to version 1.123.32, 2.17.4, or 2.18.1. Additionally, audit existing workflows using the SeaTable node to identify and remediate any instances where untrusted input flows into search or retrieval parameters.

Recommended fix High confidence

1.123.32, 2.17.4, or 2.18.1 (depending on current major version)

  1. 1. Identify all n8n instances running versions < 1.123.32, 2.17.0-2.17.3, or 2.18.0
  2. 2. Determine which version line (1.x or 2.x) is in use to select the appropriate upgrade target
  3. 3. Review the n8n release notes for the target version (1.123.32, 2.17.4, or 2.18.1) for any breaking changes
  4. 4. Create a backup of the n8n database
  5. 5. Test the upgrade in a non-production environment
  6. 6. Upgrade n8n to version 1.123.32 (for 1.x users), 2.17.4 (for 2.17.x users), or 2.18.1 (for 2.18.0 users)
  7. 7. Verify the SeaTable node's row:search and row:get operations work correctly
  8. 8. Confirm workflows using SeaTable node are functioning as expected
Caveat Review n8n release notes for version-specific breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42229 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data