n8n@2.29.6

n8n Workflow Automation Tool

  • latest version

    2.33.3

  • first published

    7 years ago

  • latest version published

    4 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
    • 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
    Cross-site Scripting (XSS)

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the HTML preview, which renders execution output into an iframe srcdoc without the sandbox attribute. An attacker can execute arbitrary scripts in the context of the application by injecting malicious content, allowing them to perform actions as the victim, such as calling authenticated APIs using the victim's session.

    Note: This is only exploitable if a user with global:member privileges opens the preview.

    How to fix Cross-site Scripting (XSS)?

    Upgrade n8n to version 1.123.64, 2.29.8, 2.30.1 or higher.

    <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1
    • H
    Cross-site Scripting (XSS)

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the Resource Locator component when the cachedResultUrl parameter is passed to window.open without proper scheme validation. An attacker can execute arbitrary scripts in the context of the victim's browser by crafting a workflow with a malicious scheme in cachedResultUrl and convincing a user with workflow access to interact with external links.

    How to fix Cross-site Scripting (XSS)?

    Upgrade n8n to version 1.123.64, 2.29.8, 2.30.1 or higher.

    <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1
    • M
    Insertion of Sensitive Information into Log File

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File in the process that handles HTTP header credentials in LLM sub-node execution data. An attacker can obtain sensitive API keys and secrets by accessing workflow execution records where these credentials are stored in plaintext.

    Note: This is only exploitable if an authenticated user has access to execution data that includes unmasked header values.

    How to fix Insertion of Sensitive Information into Log File?

    Upgrade n8n to version 1.123.64, 2.29.8, 2.30.1 or higher.

    <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1
    • M
    Incorrect Authorization

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Incorrect Authorization in the run_node_tool function in the agents module. An attacker can gain unauthorized access to credential secrets and execute arbitrary nodes by interacting with an agent that has node tools enabled, bypassing proper authorization checks.

    How to fix Incorrect Authorization?

    Upgrade n8n to version 2.29.8, 2.31.0 or higher.

    <2.29.8>=2.30.0 <2.31.0
    • 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
    • H
    Authorization Bypass Through User-Controlled Key

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key in the SSO instance-role provisioning. An attacker can gain full administrative privileges by manipulating the instance-role claim issued by the Identity Provider (IdP) during authentication.

    Note: This is only exploitable if Enterprise SSO is configured, instance-role provisioning is enabled via the N8N_SSO_SCOPES_PROVISION_INSTANCE_ROLE flag, and the attacker can control the value of the instance-role claim from the IdP.

    How to fix Authorization Bypass Through User-Controlled Key?

    Upgrade n8n to version 1.123.64, 2.29.8, 2.30.1 or higher.

    <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.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
    Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') via the legacy expression evaluator's computed-member sanitizer. An attacker can achieve host-level code execution by bypassing input sanitization as an authenticated user with workflow create or modify permissions.

    Note: This is only exploitable if the legacy expression engine is enabled as the default engine.

    How to fix Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')?

    Upgrade n8n to version 1.123.64, 2.29.8, 2.30.1 or higher.

    <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1
    • H
    Incorrect Authorization

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Incorrect Authorization in the Token Exchange process. An attacker can gain elevated privileges and execute arbitrary code by obtaining a valid external JWT accepted by a configured trusted key, which allows invoking administrator-only Public API operations such as role escalation, user creation, and user deletion.

    Note: This is only exploitable if both the Token Exchange feature and the Public API are enabled, and the attacker can obtain an external JWT trusted by a configured issuer. Role escalation additionally requires an Advanced Permissions license; Community Package installation additionally requires both N8N_COMMUNITY_PACKAGES_ENABLED=true and N8N_UNVERIFIED_PACKAGES_ENABLED=true.

    How to fix Incorrect Authorization?

    Upgrade n8n to version 2.29.8, 2.30.1 or higher.

    <2.29.8>=2.30.0 <2.30.1
    • H
    Server-side Request Forgery (SSRF)

    n8n is a n8n Workflow Automation Tool

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the /rest/dynamic-node-parameters/ endpoint due to insufficient authorization checks and the ability to supply an absolute URL in the routing configuration. An attacker can access internal network resources by making the server issue HTTP requests to arbitrary internal targets.

    Note: This is only exploitable if SSRF protection is disabled (N8N_SSRF_PROTECTION_ENABLED=false). This is the default setting.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade n8n to version 1.123.64, 2.29.8, 2.30.1 or higher.

    <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.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