n8n-nodes-base@2.4.5

Base nodes of n8n

Direct Vulnerabilities

Known vulnerabilities in the n8n-nodes-base package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free
VulnerabilityVulnerable Version
  • M
Directory Traversal

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.

How to fix Directory Traversal?

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

<2.19.3
  • C
Prototype Pollution

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.

How to fix Prototype Pollution?

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

<2.20.4>=2.21.0 <2.21.1
  • C
Prototype Pollution

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.

How to fix Prototype Pollution?

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

<2.20.4>=2.21.0 <2.21.1
  • H
Arbitrary Argument Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Arbitrary Argument Injection in a push operation. A user with permission to create or modify workflows can read arbitrary files on the server by injecting CLI flags during workflow creation or modification.

How to fix Arbitrary Argument Injection?

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

<1.121.29>=2.0.0-rc.0 <2.20.4>=2.21.0 <2.21.1
  • M
SQL Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to SQL Injection via the process of constructing SQL queries in the Snowflake and legacy MySQL v1 nodes when user-controlled input is directly interpolated into identifier fields such as table name, column name, or update key without proper escaping. An attacker can exfiltrate, modify, or delete data on the connected database by supplying crafted input through workflow expressions.

How to fix SQL Injection?

Upgrade n8n-nodes-base to version 1.121.23, 2.17.2, 2.18.1 or higher.

<1.121.23>=2.0.0-rc.0 <2.17.2>=2.18.0 <2.18.1
  • M
SQL Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to SQL Injection via the Limit field in the Oracle Database node when user-controlled input is passed through expressions without proper sanitization or parameterization. An attacker can execute arbitrary SQL commands and exfiltrate data from the connected Oracle database by injecting malicious input into the Limit field.

Note: This is only exploitable if the Oracle Database node is configured to accept external input into the Limit field, such as from a webhook, and the workflow allows unauthenticated or untrusted access.

How to fix SQL Injection?

Upgrade n8n-nodes-base to version 1.121.23, 2.17.2, 2.18.1 or higher.

<1.121.23>=2.0.0-rc.0 <2.17.2>=2.18.0 <2.18.1
  • C
Prototype Pollution

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Prototype Pollution via the xml node. An attacker can execute arbitrary code by exploiting prototype pollution when creating or modifying workflows.

Note: This is only exploitable if the attacker is an authenticated user with permissions to create or modify workflows and can combine the prototype pollution with other nodes.

How to fix Prototype Pollution?

Upgrade n8n-nodes-base to version 1.121.23, 2.17.2, 2.18.1 or higher.

<1.121.23>=2.0.0-rc.0 <2.17.2>=2.18.0 <2.18.1
  • M
SQL Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to SQL Injection via the row:search and row:get operations in the SeaTable node when user-controlled input is passed through expressions into the searchTerm or rowId parameters. An attacker can access unauthorized data from the connected SeaTable base by injecting crafted input that manipulates the underlying SQL query.

Notes: This is only exploitable if the workflow is configured to pass external user input into the affected parameters.

How to fix SQL Injection?

Upgrade n8n-nodes-base to version 1.121.23, 2.17.2, 2.18.1 or higher.

<1.121.23>=2.0.0-rc.0 <2.17.2>=2.18.0 <2.18.1
  • M
Cross-site Scripting (XSS)

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the Form Trigger node. An attacker can execute arbitrary scripts in the context of users visiting a published form by injecting malicious payloads, potentially leading to form submission hijacking and phishing attacks.

Note: The existing Content Security Policy prevents direct session cookie theft but does not stop script execution or manipulation of form actions.

How to fix Cross-site Scripting (XSS)?

Upgrade n8n-nodes-base to version 1.121.18, 2.11.2 or higher.

<1.121.18>=2.0.0-rc.0 <2.11.2
  • M
User Impersonation

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to User Impersonation via the ZendeskTrigger component. An attacker can inject arbitrary data into workflows by sending unsigned POST requests to the webhook endpoint.

How to fix User Impersonation?

Upgrade n8n-nodes-base to version 1.121.12, 2.4.6, 2.6.1 or higher.

<1.121.12>=2.0.0 <2.4.6>=2.6.0 <2.6.1
  • M
User Impersonation

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to User Impersonation via the GitHub Webhook Trigger component. An attacker can trigger unauthorized workflow executions by sending unsigned POST requests to the webhook endpoint, thereby injecting arbitrary data into the workflow.

How to fix User Impersonation?

Upgrade n8n-nodes-base to version 1.121.9, 2.5.0 or higher.

<1.121.9>=2.0.0 <2.5.0
  • H
Cross-site Scripting (XSS)

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the workflow creation and editing process in various nodes, including Form Trigger, Chat Trigger, Send & Wait, Webhook, and Chat nodes. An attacker can execute arbitrary scripts in the browsers of users who visit affected pages by injecting malicious payloads, potentially leading to session hijacking and account takeover.

How to fix Cross-site Scripting (XSS)?

Upgrade n8n-nodes-base to version 1.121.15, 2.9.1, 2.10.1 or higher.

<1.121.15>=2.0.0 <2.9.1>=2.10.0 <2.10.1
  • C
Eval Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Eval Injection. An attacker can execute arbitrary code on the host system by submitting specially crafted form data that is interpreted as an expression.

Note:

This is only exploitable if a workflow contains a form node with a field that interpolates unauthenticated user input and the field value begins with an '=' character, causing double evaluation of the content.

How to fix Eval Injection?

Upgrade n8n-nodes-base to version 1.121.15, 2.9.1, 2.10.1 or higher.

<1.121.15>=2.0.0 <2.9.1>=2.10.0 <2.10.1
  • H
Exposure of Sensitive System Information to an Unauthorized Control Sphere

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.

How to fix Exposure of Sensitive System Information to an Unauthorized Control Sphere?

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

<2.7.0
  • C
Arbitrary Code Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Arbitrary Code Injection via the Merge node's SQL query mode. An attacker can execute arbitrary code and write arbitrary files on the server by crafting malicious workflows after authenticating with permissions to create or modify workflows.

How to fix Arbitrary Code Injection?

Upgrade n8n-nodes-base to version 1.121.15, 2.9.1, 2.10.1 or higher.

<1.121.15>=2.0.0 <2.9.1>=2.10.0 <2.10.1
  • C
Command Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Command Injection via the Git node. An attacker can execute arbitrary system commands or read arbitrary files on the host by creating or modifying workflows as an authenticated user with the necessary permissions.

How to fix Command Injection?

Upgrade n8n-nodes-base to version 1.121.11, 2.5.2 or higher.

<1.121.11>=2.0.0-rc.0 <2.5.2
  • H
Command Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Command Injection via the Execute Command node. An attacker can execute arbitrary commands on the host system by leveraging access to an authenticated user account, potentially leading to data exfiltration, service disruption, or full system compromise.

Note:

This is only exploitable if the Execute Command node is enabled and not all user accounts are strictly controlled and trusted.

This issue does not impact n8n.cloud.

As per maintainers' memo: "No code changes have been made to alter the behavior of the Execute Command node. The recommended mitigation is to disable the node by default in environments where it is not explicitly required. Future n8n versions may change the default availability of this node."

##Workaround

This vulnerability can be mitigated by disabling the Execute Command node before n8n start using the environment variable: export NODES_EXCLUDE: "[\"n8n-nodes-base.executeCommand\"]".

How to fix Command Injection?

There is no fixed version for n8n-nodes-base.

>=0.1.0