2.32.6
7 years ago
23 hours ago
Known vulnerabilities in the n8n package. This does not include vulnerabilities belonging to this package’s dependencies.
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| Vulnerability | Vulnerable Version |
|---|---|
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Missing Authentication for Critical Function via the How to fix Missing Authentication for Critical Function? Upgrade | <2.27.4 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Incorrect Authorization in the How to fix Incorrect Authorization? Upgrade | <2.29.8>=2.30.0 <2.31.0 |
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 | <2.31.5>=2.32.0 <2.32.1 |
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 | <2.31.5>=2.32.0 <2.32.1 |
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 How to fix Incorrect Authorization? Upgrade | <2.29.8>=2.30.0 <2.30.1 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Improper Restriction of Communication Channel to Intended Endpoints via the AI Agents MCP verifier in Notes
Workarounds
How to fix Improper Restriction of Communication Channel to Intended Endpoints? Upgrade | <2.27.4>=2.28.0 <2.28.1 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to User Impersonation via the token-exchange identity-resolution service in Notes
Workarounds
How to fix User Impersonation? Upgrade | <2.27.4>=2.28.0 <2.28.1 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Cross-site Scripting (XSS) n the credential management flow, where the Authorization URL field of an OAuth2 credential accepts a How to fix Cross-site Scripting (XSS)? Upgrade | <2.6.4>=2.7.0 <2.8.0 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Incorrect Authorization in the Public API execution retry endpoint, which authorizes the request against the How to fix Incorrect Authorization? Upgrade | <2.25.7>=2.26.0 <2.26.2 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Incorrect Authorization in workflow creation folder assignment, which does not verify that the requested target folder belongs to a project the requester is allowed to access. A user with workflow creation permission in one project can associate a newly created workflow with a folder belonging to a different project they cannot access by submitting a crafted creation request. Exploitation requires multi-project and folder support to be enabled, and the impact is confined to a logical integrity violation of the target project's folder structure at the database level, since the workflow stays in the requester's project, remains invisible to the target project, and exposes no target project data. How to fix Incorrect Authorization? Upgrade | <2.28.0 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Incomplete List of Disallowed Inputs for the Python Code node when the Python Task Runner is enabled. A user with permission to create or modify workflows can evade the validator and reach the task executor module namespace by authoring Python in that node, and on instances configured with How to fix Incomplete List of Disallowed Inputs? Upgrade | <2.25.7>=2.26.0 <2.26.2 |
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 | * |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key in the Source Control feature when configured to use SSH, as the SSH command disables host key verification. An attacker can intercept repository data or inject malicious content by performing a man-in-the-middle attack between the affected instance and the remote Git server. How to fix Authorization Bypass Through User-Controlled Key? Upgrade | <2.5.0 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Incorrect Authorization in the OAuth callback when the How to fix Incorrect Authorization? Upgrade | <2.6.4>=2.7.0 <2.7.3 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the Credential Management Flow when a crafted OAuth2 credential contains a JavaScript URL in the Authorization URL field. An attacker can execute arbitrary scripts in the victim's browser session by convincing an authenticated user with permission to create and share credentials to interact with the OAuth authorization button. How to fix Cross-site Scripting (XSS)? Upgrade | <2.6.4>=2.7.0 <2.8.0 |
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 | <2.8.0 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Command Injection via the Note: This is only exploitable if the This issue does not impact 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 How to fix Command Injection? There is no fixed version for | >=0.0.1 |