Quick answers
- Is CVE-2026-103253 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103253 being exploited in the wild.
- How severe is CVE-2026-103253?
- High severity, with a CVSS score of 8.7, published 1 October 2026.
- Which products and versions are affected?
- N8n before 1.123.80, from 2.0.0 before 2.39.6, from 2.40.0 before 2.40.1.
- Is there a fix for CVE-2026-103253?
- Yes: fixed in 1.123.80, 2.39.6, 2.40.1. Until then: Restrict n8n instance access to fully trusted users only. Audit Oracle Database node workflows to ensure the table and schema fields are not bound to untrusted external data sources. Disable the Oracle Database node by adding n8n-nodes-base.oracleDatabase to the NODES_EXCLUDE environment variable if not required. Restrict the Oracle credential used by affected workflows to the minimum necessary database privileges. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103253 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-103253?
- Check whether you run N8n at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.123.80, 2.39.6, 2.40.1
Restrict n8n instance access to fully trusted users only. Audit Oracle Database node workflows to ensure the table and schema fields are not bound to untrusted external data sources. Disable the Oracle Database node by adding n8n-nodes-base.oracleDatabase to the NODES_EXCLUDE environment variable if not required. Restrict the Oracle credential used by affected workflows to the minimum necessary database privileges.
Technical details
The Oracle Database node's Delete Table → Drop operation fails to sanitize single quotes in the table and schema input fields before constructing a PL/SQL statement, allowing SQL injection. The vulnerability requires the attacker to have access to an n8n workflow (either direct access or control over upstream data) and the presence of a valid Oracle database credential. Successful exploitation enables execution of arbitrary DDL or DML commands with the privileges of the database credential.
Affected products
- n8n n8n before 1.123.80, from 2.0.0 before 2.39.6, from 2.40.0 before 2.40.1
Timeline
- 2026-09-16: disclosed
- 2026-10-01: advisory