n8n@2.18.0

n8n Workflow Automation Tool

  • latest version

    2.18.5

  • first published

    7 years ago

  • latest version published

    5 days ago

  • licenses detected

  • 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
    • C
    Prototype Pollution

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Prototype Pollution via the xml2js used for parsing XML request bodies in webhook handlers. An authenticated attacker with permission to create or modify workflows could exploit this to pollute the JavaScript object prototype and, by chaining the pollution with the Git node's SSH operations, achieve remote code execution on the n8n host.

    How to fix Prototype Pollution?

    Upgrade n8n to version 1.123.32, 2.17.4, 2.18.1 or higher.

    <1.123.32>=2.0.0-rc.0 <2.17.4>=2.18.0 <2.18.1
    • H
    Allocation of Resources Without Limits or Throttling

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the MCP OAuth client registration process. An attacker can exhaust server memory resources and render the instance unavailable by sending large unauthenticated registration payloads to the endpoint, which accepts requests regardless of MCP access settings.

    How to fix Allocation of Resources Without Limits or Throttling?

    A fix was pushed into the master branch but not yet published.

    *
    • M
    Missing Authorization

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Missing Authorization via the /chat WebSocket endpoint when authentication is set to None and a workflow execution is in a waiting state. An attacker can gain unauthorized access to workflow executions and influence downstream workflow behavior by attaching to an execution using a discovered execution ID and submitting arbitrary input.

    Note: This is only exploitable if the Hosted Chat workflow is publicly exposed with authentication set to None, a target execution is in a waiting state, and the attacker can obtain the execution ID.

    How to fix Missing Authorization?

    Upgrade n8n to version 1.123.32, 2.17.4, 2.18.1 or higher.

    <1.123.32>=2.0.0-rc.0 <2.17.4>=2.18.0 <2.18.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