CVE-2026-103253: n8n: SQL injection in Oracle node Drop Table operation

HIGH
Published October 1, 2026
CISO Take

n8n's Oracle Database node builds its Delete Table (Drop) statement from unsanitized table and schema fields. A single quote in either field lets an attacker append arbitrary SQL, with DDL and DML run under the connected credential's privileges. Exploitation is rated high complexity because the attacker has to control those field values, for example through upstream workflow data or an AI agent's tool inputs. The EPSS score is low (0.00232), the CVE is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK. This is a patch-in-cycle issue, not an emergency. Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later, and review any workflow that passes dynamic values into the Oracle node, especially in AI agent flows. Also check that the Oracle credentials n8n uses follow least privilege, since the blast radius equals those rights.

Sources:NVDEPSSGitHub Advisoryvulncheck.comATLASCISA SSVC

What is the risk?

Overall risk is MEDIUM-HIGH, driven by impact more than likelihood. CVSS 8.7 reflects a scope change with high integrity and availability impact: arbitrary DDL/DML, including dropping tables or altering data. Exploitability is limited by high attack complexity, the need for attacker-influenced input to reach the node, and no known public exploit. EPSS is 0.00232, the CVE is not in CISA KEV, and SSVC says TRACK. Exposure rises where n8n is internet-facing or where LLM agents or webhooks feed untrusted data into the Oracle node's table or schema parameters. Confidence: HIGH on the vulnerability facts, MEDIUM on real-world exposure (dependents and deployment data unknown).

How does the attack unfold?

Initial Access
Attacker supplies a crafted table or schema value through a webhook, form, or agent-controlled input that reaches the Oracle node.
AML.T0049
Exploitation
A single quote in the table or schema field breaks out of the Drop Table statement and appends arbitrary SQL.
AML.T0053
Impact
Injected DDL/DML runs under the Oracle credential's privileges, dropping or altering tables that AI pipelines rely on.
AML.T0101

What systems are affected?

PackageEcosystemVulnerable RangePatched
n8nnpm—No patch
210.5KOpenSSF 7.116 dependentsPushed 3d ago42% patched~19d to patchFull package profile →

Do you use n8n? You're affected.

How severe is it?

CVSS 3.1
8.7 / 10
EPSS
0.2%
chance of exploitation in 30 days
Higher than 14% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Moderate

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACHigh
PRNone
UINone
SChanged
CNone
IHigh
AHigh

What should I do?

1 step
  1. 1) Upgrade n8n to 1.123.80, 2.39.6, or 2.40.1 or later, depending on your branch. 2) Inventory workflows that use the Oracle Database node's Delete Table (Drop) operation and check whether table or schema fields come from webhooks, forms, or LLM/agent outputs. 3) Until patched, disable or remove that operation, or hardcode table and schema names and validate them against an allowlist. 4) Reduce the Oracle credential to least privilege (no DROP/ALTER or schema-level rights unless required). 5) Detection: monitor Oracle audit logs for unexpected DDL (DROP, ALTER, CREATE) and stacked statements from the n8n service account, and review n8n execution logs for field values containing single quotes. 6) Restrict network exposure of the n8n instance and its webhooks.

What does CISA's SSVC say?

DecisionTrack
Exploitationnone
AutomatableNo
Technical Impactpartial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001
A.6.2.6-AI system operation and monitoring
NIST AI RMF
MANAGE 2.3-Responses to previously unknown or newly identified risks and vulnerabilities are planned and in place
OWASP LLM Top 10
LLM06-Excessive Agency

Frequently Asked Questions

What is CVE-2026-103253?

n8n's Oracle Database node builds its Delete Table (Drop) statement from unsanitized table and schema fields. A single quote in either field lets an attacker append arbitrary SQL, with DDL and DML run under the connected credential's privileges. Exploitation is rated high complexity because the attacker has to control those field values, for example through upstream workflow data or an AI agent's tool inputs. The EPSS score is low (0.00232), the CVE is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK. This is a patch-in-cycle issue, not an emergency. Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later, and review any workflow that passes dynamic values into the Oracle node, especially in AI agent flows. Also check that the Oracle credentials n8n uses follow least privilege, since the blast radius equals those rights.

Is CVE-2026-103253 actively exploited?

No confirmed active exploitation of CVE-2026-103253 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-103253?

1) Upgrade n8n to 1.123.80, 2.39.6, or 2.40.1 or later, depending on your branch. 2) Inventory workflows that use the Oracle Database node's Delete Table (Drop) operation and check whether table or schema fields come from webhooks, forms, or LLM/agent outputs. 3) Until patched, disable or remove that operation, or hardcode table and schema names and validate them against an allowlist. 4) Reduce the Oracle credential to least privilege (no DROP/ALTER or schema-level rights unless required). 5) Detection: monitor Oracle audit logs for unexpected DDL (DROP, ALTER, CREATE) and stacked statements from the n8n service account, and review n8n execution logs for field values containing single quotes. 6) Restrict network exposure of the n8n instance and its webhooks.

What systems are affected by CVE-2026-103253?

This vulnerability affects the following AI/ML architecture patterns: Agent frameworks, Workflow automation platforms, RAG pipelines, Data preparation pipelines.

What is the CVSS score for CVE-2026-103253?

CVE-2026-103253 has a CVSS v3.1 base score of 8.7 (HIGH). The EPSS exploitation probability is 0.23%.

What is the AI security impact?

Affected AI Architectures

Agent frameworksWorkflow automation platformsRAG pipelinesData preparation pipelines

MITRE ATLAS Techniques

AML.T0049Exploit Public-Facing Application
AML.T0053AI Agent Tool Invocation
AML.T0101Data Destruction via AI Agent Tool Invocation

Compliance Controls Affected

ISO 42001: A.6.2.6
NIST AI RMF: MANAGE 2.3
OWASP LLM Top 10: LLM06

What are the technical details?

Original Advisory

n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain an SQL injection vulnerability in the Oracle Database node's Delete Table Drop operation. Attackers can inject single quotes in the table or schema fields to append arbitrary SQL statements and execute DDL or DML commands against the connected database with the credential's privileges.

Exploitation Scenario

An organization runs an n8n workflow where an LLM agent or a public webhook supplies the table name for a cleanup step against an Oracle database that backs an AI analytics or RAG pipeline. An attacker submits a crafted value containing a single quote and appended SQL, either directly to the webhook or through prompt content that steers the agent's tool parameters. The Oracle node concatenates the value into the DROP statement, and the injected statements run with the n8n credential's privileges. The attacker drops or modifies tables, tampers with data used by downstream models, or causes an outage of dependent AI services.

Weaknesses (CWE)

CWE-89 — Improper Neutralization of Special Elements used in an SQL Command: The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

  • [Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.
  • [Architecture and Design] If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. Process SQL queries using prepared statements, parameterized queries, or stored procedures. These features should accept parameters or variables and support strong typing. Do not dynamically construct and execute query strings within these features using "exec" or similar functionality, since this may re-introduce the possibility of SQL injection. [REF-867]

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H

Timeline

Published
October 1, 2026
Last Modified
October 1, 2026
First Seen
October 1, 2026

Related Vulnerabilities