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
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.
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 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.
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
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.