Homepage

n8n@2.31.4

n8n Workflow Automation Tool

  • latest version

    2.32.6

  • first published

    7 years ago

  • latest version published

    14 hours 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
    Incorrect Authorization

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Incorrect Authorization via the genericAuthType in the HTTP Request node. An attacker can gain unauthorized access to credentials belonging to other users by referencing another user's credential through an expression, which bypasses the intended ownership check during execution.

    Note: This is only exploitable if the attacker knows the identifier of the target credential.

    How to fix Incorrect Authorization?

    Upgrade n8n to version 1.123.67, 2.31.5, 2.32.1 or higher.

    <1.123.67>=2.0.0-rc.0 <2.31.5>=2.32.0 <2.32.1
    • H
    Incorrect Authorization

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Incorrect Authorization in the authentication when the embed login feature is enabled and at least one trusted key source is configured. An attacker can gain unauthorized access to any existing user account by presenting a validly-signed token with an unverified email claim from a trusted issuer.

    Note: This is only exploitable if the embed login feature is enabled and at least one trusted key source is configured.

    How to fix Incorrect Authorization?

    Upgrade n8n to version 2.31.5, 2.32.1 or higher.

    <2.31.5>=2.32.0 <2.32.1
    • M
    Incorrect Authorization

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Incorrect Authorization in the process that handles credential domain restrictions when user-supplied base or endpoint URLs are set. An attacker can exfiltrate credential secrets by configuring affected nodes to send secrets to an attacker-controlled host.

    Note: This is only exploitable if a credential has domain restrictions configured and is shared with non-owner users.

    How to fix Incorrect Authorization?

    Upgrade n8n to version 2.31.5, 2.32.1 or higher.

    <2.31.5>=2.32.0 <2.32.1
    • M
    Incorrect Authorization

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Incorrect Authorization in the JS task runner. An attacker can impact the confidentiality, integrity, or availability of other users' executions by poisoning the shared module cache.

    Note: This is only exploitable if the instance is multi-user and the JS task runner is configured with built-in or external modules enabled.

    How to fix Incorrect Authorization?

    Upgrade n8n to version 1.123.67, 2.31.5, 2.32.1 or higher.

    <1.123.67>=2.0.0-rc.0 <2.31.5>=2.32.0 <2.32.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.

    *
    • 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