Homepage

n8n-nodes-base@1.121.31

Base nodes of n8n

  • latest version

    2.15.1

  • first published

    6 years ago

  • latest version published

    1 months ago

  • licenses detected

  • View n8n-nodes-base package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    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
    • M
    SQL Injection

    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.

    How to fix SQL Injection?

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

    <2.4.0
    • 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
    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
    Remote Code Execution (RCE)

    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.

    How to fix Remote Code Execution (RCE)?

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

    >=1.0.0 <2.0.0-rc.1
    • 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
    Go back to all versions of this package