Skip to content
Noroxi
CVE-2026-42229· NVD / CVE Program· CNA GitHub_M

n8n: SQL Injection in SeaTable Node

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.

MediumCVSS 5.3 · v4.0—No exploit Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
May 4, 2026
Updated
Jun 17, 2026
EPSS
0.6% · 46th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
5.3
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
n8nn8n

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • n8n n8nbefore 1.123.32
  • n8n n8n2.17.0 and later · before 2.17.4
  • n8n n8n2.18.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • n8n-io n8n

    • < 1.123.32, >= 2.17.0, < 2.17.4, >= 2.18.0, < 2.18.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmn8nfrom 2.0.0 · before 2.17.42.17.4
npmn8nfrom 2.18.0 · before 2.18.12.18.1
npmn8nbefore 1.123.321.123.32

Same product

n8n: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-68613n8n Vulnerable to Remote Code Execution via Expression InjectionKEV
    95Now
  • CVE-2026-21858n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling
    64This week
  • CVE-2026-1470Authenticated users can bypass the Expression sandbox mechanism to achieve full remote code execution on n8n’s main node.
    45Plan
  • CVE-2025-68668n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node
    43Plan
  • CVE-2026-0863Sandbox escape in n8n Python task runner allows for arbitrary code execution on the underlying host.
    42Plan
  • CVE-2026-21877n8n is vulnerable to Remote Code Execution via Arbitrary File Write
    41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:n8n1.123.32Package registry (OSV)
npm:n8n2.17.4Package registry (OSV)
npm:n8n2.18.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-2749768 days apartn8n has Potential Remote Code Execution via Merge Node
    37Monitor
  • CVE-2026-4479250 days apartn8n: Source Control Pull SQL Injection
    35Monitor
  • CVE-2026-3371340 days apartn8n Vulnerable to SQL Injection in Data Table Node via orderByColumn Expression
    34Monitor
  • CVE-2026-77071108 days apartn8n before 1.123.69 PostgREST Filter Injection via Supabase
    28Monitor
  • CVE-2026-5431050 days apartn8n: SQL Injection in Postgres v1/TimesclaeDB Nodes
    26Monitor
  • CVE-2026-5431350 days apartn8n: NoSQL Injection in MongoDB Node Find And Replace Operation
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • CVE-2026-422300 days apartn8n: Open Redirect in MCP OAuth Consent Flow
    20Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = '" + owner + "'");

Fixed

ts
const owner = req.query.owner;const rows = await db.query(  "SELECT * FROM files WHERE owner = $1",  [owner]);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records