n8n-nodes-base 2.1.4 vulnerabilities

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

Vulnerability	Vulnerable Version
C Protection Mechanism Failure 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). How to fix Protection Mechanism Failure? Upgrade `n8n-nodes-base` to version 2.3.0 or higher.	<2.3.0
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
C Arbitrary File Upload n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Arbitrary File Upload via the Merge node's SQL Query mode. An attacker can write arbitrary files to the server's filesystem and potentially execute remote code by crafting malicious workflows. Note: This is only exploitable if the attacker has authenticated access with permissions to create or modify workflows. How to fix Arbitrary File Upload? Upgrade `n8n-nodes-base` to version 1.121.12, 2.4.0 or higher.	<1.121.12>=2.0.0 <2.4.0
H Directory Traversal n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Directory Traversal via the SSH node when workflows process uploaded files and transfer them to remote servers without validating their metadata. An attacker can write files to unintended locations on remote systems and potentially achieve remote code execution by uploading specially crafted files to unauthenticated endpoints. Note: This is only exploitable if the attacker has knowledge of such workflows and the endpoints for file uploads are unauthenticated. How to fix Directory Traversal? Upgrade `n8n-nodes-base` to version 1.121.7, 2.3.2 or higher.	<1.121.7>=2.0.0 <2.3.2
M Permissive List of Allowed Inputs n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Permissive List of Allowed Inputs in the Webhook Node's IP whitelist validation due to `includes()` method performing partial string matching instead of exact IP comparison. An attacker can gain unauthorized access to restricted endpoints by sending requests from an IP address that partially matches a whitelisted entry, thereby bypassing intended access controls. How to fix Permissive List of Allowed Inputs? Upgrade `n8n-nodes-base` to version 1.121.7, 2.2.0 or higher.	>=1.36.0 <1.121.7>=2.0.0-rc.0 <2.2.0
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

Vulnerability

Vulnerable Version

Protection Mechanism Failure

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).

How to fix Protection Mechanism Failure?

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

<2.3.0

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

Arbitrary File Upload

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Arbitrary File Upload via the Merge node's SQL Query mode. An attacker can write arbitrary files to the server's filesystem and potentially execute remote code by crafting malicious workflows.

Note:

This is only exploitable if the attacker has authenticated access with permissions to create or modify workflows.

How to fix Arbitrary File Upload?

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

<1.121.12>=2.0.0 <2.4.0

Directory Traversal

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Directory Traversal via the SSH node when workflows process uploaded files and transfer them to remote servers without validating their metadata. An attacker can write files to unintended locations on remote systems and potentially achieve remote code execution by uploading specially crafted files to unauthenticated endpoints.

Note:

This is only exploitable if the attacker has knowledge of such workflows and the endpoints for file uploads are unauthenticated.

How to fix Directory Traversal?

Upgrade n8n-nodes-base to version 1.121.7, 2.3.2 or higher.

<1.121.7>=2.0.0 <2.3.2

Permissive List of Allowed Inputs

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Permissive List of Allowed Inputs in the Webhook Node's IP whitelist validation due to includes() method performing partial string matching instead of exact IP comparison. An attacker can gain unauthorized access to restricted endpoints by sending requests from an IP address that partially matches a whitelisted entry, thereby bypassing intended access controls.

How to fix Permissive List of Allowed Inputs?

Upgrade n8n-nodes-base to version 1.121.7, 2.2.0 or higher.

>=1.36.0 <1.121.7>=2.0.0-rc.0 <2.2.0

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

n8n-nodes-base@2.1.4 vulnerabilities

Base nodes of n8n

latest version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically