Homepage

n8n@1.123.11 vulnerabilities

n8n Workflow Automation Tool

  • latest version

    2.9.4

  • first published

    6 years ago

  • latest version published

    3 days ago

  • licenses detected

  • View n8n package health on Snyk Advisor  (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
    • M
    Improper Authentication

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Improper Authentication via the Self-Service Settings API. An attacker can circumvent centralized identity management and multi-factor authentication by disabling SSO enforcement for their own account and creating local credentials after authenticating through SSO.

    How to fix Improper Authentication?

    Upgrade n8n to version 2.8.0 or higher.

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