n8n: SQL Injection via Metadata Filter Key in the Vector Store (OracleDB) Node

Impact

The Vector Store (OracleDB) node did not validate Metadata Filter keys, allowing SQL injection into the vector search query. In workflows where untrusted input (e.g., from a webhook) is passed into the filter key, an attacker could read data accessible to the configured Oracle credential.

Patches

The issue has been fixed in n8n versions 2.44.1, 2.43.5 and 3.0.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

• Restrict n8n instance access to fully trusted users only.
• Audit active workflows that use the Vector Store (OracleDB) node and ensure the Metadata Filter Name field does not incorporate untrusted external data via expressions.
• Apply network-level controls to restrict access to webhook endpoints that feed into these workflows.
• Deactivate affected workflows until the instance is patched.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.