Homepage

n8n@2.14.0

n8n Workflow Automation Tool

  • latest version

    2.15.1

  • first published

    6 years ago

  • latest version published

    3 days ago

  • licenses detected

  • View n8n 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 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
    • H
    Cross-site Scripting (XSS)

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the /rest/binary-data endpoint when serving HTML binary data objects without a filename, as the response lacks Content-Disposition and Content-Security-Policy headers. An attacker can execute arbitrary JavaScript in the context of a higher-privileged user's authenticated session by sending a crafted URL, potentially leading to exfiltration or modification of sensitive data, or privilege escalation.

    How to fix Cross-site Scripting (XSS)?

    Upgrade n8n to version 1.123.27, 2.13.3, 2.14.1 or higher.

    <1.123.27>=2.0.0-rc.0 <2.13.3>=2.14.0 <2.14.1
    • H
    Prototype Pollution

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Prototype Pollution via the GSuiteAdmin node parameter. An attacker with permissions to create or modify workflows can execute arbitrary code by supplying crafted parameters that pollute Object.prototype during workflow creation or modification.

    How to fix Prototype Pollution?

    Upgrade n8n to version 1.123.27, 2.13.3, 2.14.1 or higher.

    <1.123.27>=2.0.0-rc.0 <2.13.3>=2.14.0 <2.14.1
    • H
    SQL Injection

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to SQL Injection in the orderByColumn expression of the Data Table Get node. An attacker with permissions to create or modify workflows can execute arbitrary SQL commands by supplying crafted input, potentially leading to unauthorized data access, modification, or deletion.

    Note: This is only exploitable if the Data Table node is enabled.

    How to fix SQL Injection?

    Upgrade n8n to version 1.123.27, 2.13.3, 2.14.1 or higher.

    <1.123.27>=2.0.0-rc.0 <2.13.3>=2.14.0 <2.14.1
    • H
    Arbitrary Code Injection

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Arbitrary Code Injection via the Merge node's Combine by SQL mode. An authenticated user with permissions to create or modify workflows can execute arbitrary code and access sensitive files on the host by crafting malicious SQL statements when creating or modifying workflows.

    How to fix Arbitrary Code Injection?

    Upgrade n8n to version 1.123.27, 2.13.3, 2.14.1 or higher.

    <1.123.27>=2.0.0-rc.0 <2.13.3>=2.14.0 <2.14.1
    • H
    Command Injection

    n8n is a n8n Workflow Automation Tool

    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.

    >=0.0.1
    Go back to all versions of this package