n8n-nodes-base@2.0.2 vulnerabilities

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
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
  • M
User Impersonation

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to User Impersonation via the Stripe Trigger node that does not verify incoming webhook requests against Stripe webhook signing secret. An attacker with valid webhook URL can execute unauthorized workflows by sending forged webhook events to the endpoint, bypassing signature verification.

##Workaround This vulnerability can be partially mitigated by deactivating affected workflows or restricting access to workflows containing Stripe Trigger nodes to trusted users only.

How to fix User Impersonation?

Upgrade n8n-nodes-base to version 1.121.5, 2.1.4, 2.2.2 or higher.

>=0.147.0 <1.121.5>=2.0.0-rc.0 <2.1.4>=2.2.0 <2.2.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