n8n-nodes-base@1.121.43

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to SQL Injection through the prepareItems logic used by the findOneAndReplace, findOneAndUpdate, and update operations in GenericFunctions.ts and MongoDb.node.ts. An authenticated workflow editor can supply a non-scalar updateKey value, such as an object or array, enabling the node to build a MongoDB query filter from attacker-controlled input. This lets the attacker match unintended documents and overwrite them with content of their choosing. For users running affected workflows, this can corrupt or replace data in MongoDB collections without the node rejecting the malicious filter value.

Workarounds

• Limit workflow creation and editing permissions to fully trusted users only; this prevents authenticated workflow editors from supplying a malicious updateKey value in the MongoDB node’s Find And Replace path.
• Disable the MongoDB node by adding n8n-nodes-base.mongoDb to the NODES_EXCLUDE environment variable; this blocks use of the vulnerable MongoDB node operations entirely.

Upgrade n8n-nodes-base to version 2.24.0 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Prototype Pollution via the Microsoft SQL node’s createTableStruct and related table-grouping logic in MicrosoftSql.node.ts and GenericFunctions.ts. An authenticated user who can create or modify workflows can trigger it by supplying a crafted table parameter such as __proto__, constructor, or prototype when configuring the Microsoft SQL node. That attacker-controlled table name is used as an object key in plain objects, allowing inherited properties on Object.prototype to be polluted process-wide for the life of the n8n server process. The result is application-wide validation failures and a broken n8n instance that remains non-functional until restarted.

Workarounds

• Limit workflow creation and editing permissions to fully trusted users only; this prevents untrusted authenticated users from supplying crafted table values through the Microsoft SQL node.
• Disable the Microsoft SQL node by adding n8n-nodes-base.microsoftSql to the NODES_EXCLUDE environment variable; this blocks the vulnerable node from being used to trigger the prototype-pollution path.

Upgrade n8n-nodes-base to version 2.24.0 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Exposure of Data Element to Wrong Session via the combineBySql Merge-node SQL Query path in combineBySql.ts. An authenticated attacker can poison the shared SQL sandbox by supplying a workflow that runs attacker-controlled SQL, causing prototype mutations to persist into later Merge SQL executions on the same instance. This allows the attacker to intercept data processed by other users’ workflows, breaking the isolation of workflow execution in multi-user n8n instances.

Notes

• This only affects multi-user n8n deployments where more than one user can create or execute workflows using Merge node SQL Query mode; single-user instances do not have the same cross-user persistence issue.
• The vulnerable path is the cached shared SQL sandbox used by repeated Merge SQL executions, so pollution can persist across later runs on the same instance rather than being limited to a single workflow execution.

Workarounds

• Limit workflow creation and editing permissions to fully trusted users only.
• Disable the Merge node by adding n8n-nodes-base.merge to the NODES_EXCLUDE environment variable.

Upgrade n8n-nodes-base to version 2.25.2, 2.26.5 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Improper Handling of Highly Compressed Data (Data Amplification) via the Decompress operation in the Compression node. An attacker can cause the process to terminate and disrupt all workflows by sending a specially crafted compressed archive to a public webhook workflow, leading to memory exhaustion.

Upgrade n8n-nodes-base to version 2.23.0 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the webhook verification endpoints in the Meta, WhatsApp and Microsoft Teams trigger nodes, where a query parameter is reflected into the HTTP response without proper sanitization or Content-Security-Policy headers. An attacker can execute arbitrary JavaScript in the context of a logged-in user's browser by convincing the user to visit a specially crafted URL.

Upgrade n8n-nodes-base to version 2.24.0 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Directory Traversal via the ExecuteWorkflow node's localFile source option. An attacker can enumerate arbitrary files on the server host and in some instances can achieve arbitrary code execution by uploading a specially crafted file to the host.

Upgrade n8n-nodes-base to version 2.19.3 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Prototype Pollution via the pagination parameter in the HTTP Request node. An attacker can execute arbitrary code on the instance by achieving global prototype pollution and chaining this with other techniques. This is only exploitable if the attacker is an authenticated user with permission to create or modify workflows.

Upgrade n8n-nodes-base to version 2.20.4, 2.21.1 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Prototype Pollution in the Xml class, which implements an XML node. A user with permission to create or modify workflows can achieve remote code execution on the host system.

Note: This is a bypass of the fix for the vulnerability described in CVE-2026-42232.

Upgrade n8n-nodes-base to version 2.20.4, 2.21.1 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to SQL Injection via the MySQL, PostgreSQL, and Microsoft SQL nodes due to improper escaping of identifier values. An attacker can execute arbitrary SQL commands by supplying specially crafted table or column names through node configuration parameters.

Upgrade n8n-nodes-base to version 2.4.0 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Exposure of Sensitive System Information to an Unauthorized Control Sphere due to insufficient restrictions in the Python Code node sandbox. An attacker can access sensitive files or execute arbitrary code by escaping the sandbox environment.

Upgrade n8n-nodes-base to version 2.7.0 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Protection Mechanism Failure via the Python Code node. An attacker can execute arbitrary code outside the intended security boundary by leveraging authenticated access and enabling Task Runners with Python support. This is only exploitable if Task Runners are enabled (N8N_RUNNERS_ENABLED=true), Python support is enabled (N8N_PYTHON_ENABLED=true), and the Code Node is enabled (default: true).

Upgrade n8n-nodes-base to version 2.3.0 or higher.

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Remote Code Execution (RCE) due to insufficient isolation in the Python Code Node that uses Pyodide. An authenticated attacker with permissions to create or modify workflows can execute arbitrary commands on the host system by creating or modifying workflows with malicious code.

Upgrade n8n-nodes-base to version 2.0.0-rc.1 or higher.