Kurz gesagt
- CVE-2026-42233 ist eine Schwachstelle (KRITISCH (CVSS 9.8)) in n8n (n8n), n8n.
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.33%, höher als bei 25.8% aller Schwachstellen.
- Abhilfe: auf 2.17.4, 1.123.32, 2.18.1 oder neuer aktualisieren.
| Package | Affected versions | Patched versions |
|---|
| n8n | = 2.18.0≥ 2.17.0, < 2.17.4< 1.123.32
| 2.17.41.123.32
|
| n8n npm | ≥ 2.0.0, < 2.17.4≥ 2.18.0, < 2.18.1< 1.123.32
| 2.17.42.18.11.123.32
|
Description
Impact
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.
Exploitation requires a specific workflow configuration:
- The Oracle Database node must be used with user-controlled input passed via expressions into the
Limit field.
- Authentication requirements depend on the workflow's configuration (e.g., an unauthenticated webhook endpoint would allow unauthenticated exploitation).
Patches
The issue has been fixed in n8n versions 1.123.32, 2.17.4, and 2.18.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Disable the Oracle Database node by adding
n8n-nodes-base.oracleDatabase to the NODES_EXCLUDE environment variable.
- Avoid passing unvalidated external user input into the Oracle Database node's
Limit field via expressions.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
NVD 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 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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free