UTC
High

SQL Injection in Oracle Database Node Delete Table Drop Operation

GHSA-4wf3-rgqr-xcp3 · published 2026-09-16

Severity
High
CVSS score
7.0
Chance of exploitation (EPSS)
No CVE
Fixed in
2.40.1
What it is

The Oracle Database node's Delete Table → Drop operation inserts the table and schema values into a dynamically built PL/SQL statement without neutralising single quotes, so a quote in either field appends attacker-chosen SQL to what runs. Both fields can be bound to upstream data by expression. Where one is bound to an untrusted source, whoever controls that data can run DDL or DML against the connected database, bounded by the credential's privileges — demonstrated as the unrecoverable drop of an arbitrary table. No confidentiality impact was shown.

What to do

Upgrade n8n to 2.40.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

The issue has been fixed in n8n versions 1.123.80, 2.39.6, and 2.40.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

If you cannot upgrade yet

If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict n8n instance access to fully trusted users only. Audit Oracle Database node workflows and 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 it is not required. Restrict the Oracle credential used by affected workflows to the minimum necessary privileges. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 1.123.801.123.80
n8nnpm< 2.39.62.39.6
n8nnpm< 2.40.12.40.1

The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].