2.33.3
7 years ago
4 days 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 Incorrect Authorization via the Note: This is only exploitable if the attacker knows the identifier of the target credential. How to fix Incorrect Authorization? Upgrade | <1.123.67>=2.0.0-rc.0 <2.31.5>=2.32.0 <2.32.1 |
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 Note: This is only exploitable if a user with How to fix Cross-site Scripting (XSS)? Upgrade | <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1 |
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 How to fix Cross-site Scripting (XSS)? Upgrade | <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1 |
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 | <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1 |
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 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 How to fix Authorization Bypass Through User-Controlled Key? Upgrade | <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1 |
n8n is a n8n Workflow Automation Tool Affected versions of this package are vulnerable to Incorrect Authorization in the 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 | <1.123.67>=2.0.0-rc.0 <2.31.5>=2.32.0 <2.32.1 |
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 | <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.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 Server-side Request Forgery (SSRF) in the Note: This is only exploitable if SSRF protection is disabled ( How to fix Server-side Request Forgery (SSRF)? Upgrade | <1.123.64>=2.0.0-rc.0 <2.29.8>=2.30.0 <2.30.1 |
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 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 |