| Package | Affected versions | Patched versions |
|---|---|---|
| n8n | = 2.18.0≥ 2.17.0, < 2.17.4< 1.123.32 | 2.17.41.123.32 |
| n8n | ≥ 2.0.0, < 2.17.4≥ 2.18.0, < 2.18.1< 1.123.32 | 2.17.42.18.11.123.32 |
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:
Limit field.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.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
n8n-nodes-base.oracleDatabase to the NODES_EXCLUDE environment variable.Limit field via expressions.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free