CVE-2026-42233

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.

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).

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2026-42233 has a CVSS score of 9.8 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.123.32, 2.18.1, 2.17.4); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-42233? CVE-2026-42233 is a medium-severity improper input validation vulnerability in n8n (npm), affecting versions < 1.123.32. It is fixed in 1.123.32, 2.18.1, 2.17.4. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2026-42233? CVE-2026-42233 has a CVSS score of 9.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by CVE-2026-42233? n8n (npm) versions < 1.123.32 is affected.
4. Is there a fix for CVE-2026-42233? Yes. CVE-2026-42233 is fixed in 1.123.32, 2.18.1, 2.17.4. Upgrade to this version or later.
5. Is CVE-2026-42233 exploitable, and should I be worried? Whether CVE-2026-42233 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-42233 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-42233?
   • Upgrade n8n to 1.123.32 or later
   • Upgrade n8n to 2.18.1 or later
   • Upgrade n8n to 2.17.4 or later