n8n 1.123.38

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

Vulnerability	Vulnerable Version
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 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 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 `n8n` to version 2.5.0 or higher.	<2.5.0
M Incorrect Authorization n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Incorrect Authorization in the OAuth callback when the `N8N_SKIP_AUTH_ON_OAUTH_CALLBACK` environment variable is set to `true`. An attacker can gain unauthorized access to OAuth tokens by tricking a victim into completing an OAuth flow against a credential object controlled by the attacker, allowing the attacker to execute workflows as the victim. How to fix Incorrect Authorization? Upgrade `n8n` to version 2.6.4, 2.7.3 or higher.	<2.6.4>=2.7.0 <2.7.3
M Cross-site Scripting (XSS) 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 `n8n` to version 2.6.4, 2.8.0 or higher.	<2.6.4>=2.7.0 <2.8.0
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

Vulnerability

Vulnerable Version

Allocation of Resources Without Limits or Throttling