N8N · GHSA-2x68-96jw-5r6c · AI agents & MCP
FIX → >= 2.44.1 +2
The Vector Store (OracleDB) node in n8n does not validate Metadata Filter keys, so they are inserted into the vector search SQL query. When a workflow passes untrusted input such as a webhook payload into that filter key, an attacker can read data the configured Oracle credential can access.
first public Oct 28, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only n8n instances that run workflows using the Vector Store (OracleDB) node where the Metadata Filter key takes untrusted input, typically from a webhook. Instances without that node or without external data reaching the filter key are not exposed through this path. The advisory's workarounds are short-term only: restrict access, audit workflows, limit webhook exposure or deactivate the affected workflows until patched.
Not affected if filter-key-static, no-oracledb-vector-store-node, patched-version
Who cares n8n, oracle, self-hosted, vector-store, webhook
n8n --version or the instance settings; versions below 2.44.1, 2.43.5 and 3.0.1 on their respective lines are affected.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.
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.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to >= 2.44.1 +2
2.44.1 (2.x line)2.43.5 (2.43 line)3.0.1 (3.x line)