dbcve.org
N8nApplication

CVE-2026-42233

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Oracle Database node's select operation allowed user-controlled input passed into the Limit field via expressions to be interpolated directly into the SQL query without sanitization or parameterization. In workflows where external input is passed into the Limit field (e.g., from a webhook), an attacker could inject arbitrary SQL and exfiltrate data from the connected Oracle database. 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 Oracle Database node in n8n allows user input to the Limit field to be directly interpolated into SQL queries without parameterization or sanitization, enabling SQL injection attacks when external input (e.g., from webhooks) is passed to this field.

MitigationUpgrade n8n to versions 1.123.32, 2.17.4, or 2.18.1 or later. Additionally, avoid passing untrusted external input directly into the Limit field of Oracle Database nodes until the upgrade is applied.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify n8n installation version
    Run the command 'n8n --version' or check the version in the UI footer / package.json file
    Affected if The version is less than 1.123.32, OR between 2.17.0 and 2.17.4 (exclusive), OR exactly 2.18.0
  2. Locate Oracle Database nodes in workflows
    Open each workflow in n8n and search for nodes of type 'n8n-nodes-base.oracle' or examine workflow JSON files for 'oracle' node references
    Affected if Any workflow contains an Oracle Database node
  3. Inspect Oracle Database node Limit field usage
    Open Oracle Database nodes in edit mode and examine the Limit field value - check if it contains expressions ({{ }}) that reference webhook data, HTTP Request nodes, or other external input
    Affected if The Limit field contains dynamic expressions referencing external input sources (e.g., {{ $json.body.limit }} or similar webhook/input expressions)
  4. Verify external input can reach the Limit field
    Test the workflow with crafted webhook/API input to the Limit parameter and observe if it modifies the SQL query behavior directly
    Affected if External input passed to the workflow can be inserted directly into the LIMIT clause of the generated SQL query without sanitization

You are affected if your n8n version falls within the affected ranges AND you have Oracle Database nodes with the Limit field accepting external/input 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 versions 1.123.32, 2.17.4, or 2.18.1 or later. Additionally, avoid passing untrusted external input directly into the Limit field of Oracle Database nodes until the upgrade is applied.

Recommended fix High confidence

Upgrade to n8n version 1.123.32 (for 1.x branch), 2.17.4 (for 2.17.x branch), or 2.18.1 (for 2.18.x branch)

  1. 1. Identify the current n8n version by checking the running instance (e.g., via the UI at Settings > About, or using the CLI: n8n --version)
  2. 2. Determine which release branch the current version belongs to (1.x.x or 2.x.x)
  3. 3. Upgrade to the appropriate fixed version based on the current branch: For 1.x.x versions, upgrade to 1.123.32 or later; For 2.x.x versions (2.17.0-2.17.3), upgrade to 2.17.4 or later; For version 2.18.0, upgrade to 2.18.1 or later
  4. 4. After upgrading, verify the Oracle Database node's Limit field no longer allows unsanitized SQL injection through expression inputs
  5. 5. Test workflows that use external input (e.g., webhooks) into the Limit field to confirm the vulnerability is remediated
  6. 6. If using self-hosted n8n, restart the service after upgrade to ensure the patched version is running
Caveat Review the n8n release notes for the target version to check for any breaking changes or migration requirements specific to your workflow configurations

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42233 — 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-42233 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