2.15.1
6 years ago
1 months ago
Known vulnerabilities in the n8n-nodes-base 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-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Directory Traversal via the How to fix Directory Traversal? Upgrade | <2.19.3 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Prototype Pollution via the How to fix Prototype Pollution? Upgrade | <2.20.4>=2.21.0 <2.21.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Prototype Pollution in the Note: This is a bypass of the fix for the vulnerability described in CVE-2026-42232. How to fix Prototype Pollution? Upgrade | <2.20.4>=2.21.0 <2.21.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Arbitrary Argument Injection in a push operation. A user with permission to create or modify workflows can read arbitrary files on the server by injecting CLI flags during workflow creation or modification. How to fix Arbitrary Argument Injection? Upgrade | <1.121.29>=2.0.0-rc.0 <2.20.4>=2.21.0 <2.21.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to SQL Injection via the process of constructing SQL queries in the Snowflake and legacy MySQL v1 nodes when user-controlled input is directly interpolated into identifier fields such as table name, column name, or update key without proper escaping. An attacker can exfiltrate, modify, or delete data on the connected database by supplying crafted input through workflow expressions. How to fix SQL Injection? Upgrade | <1.121.23>=2.0.0-rc.0 <2.17.2>=2.18.0 <2.18.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to SQL Injection via the Note: This is only exploitable if the Oracle Database node is configured to accept external input into the How to fix SQL Injection? Upgrade | <1.121.23>=2.0.0-rc.0 <2.17.2>=2.18.0 <2.18.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Prototype Pollution via the Note: This is only exploitable if the attacker is an authenticated user with permissions to create or modify workflows and can combine the prototype pollution with other nodes. How to fix Prototype Pollution? Upgrade | <1.121.23>=2.0.0-rc.0 <2.17.2>=2.18.0 <2.18.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to SQL Injection via the Notes: This is only exploitable if the workflow is configured to pass external user input into the affected parameters. How to fix SQL Injection? Upgrade | <1.121.23>=2.0.0-rc.0 <2.17.2>=2.18.0 <2.18.1 |
n8n-nodes-base is a Base nodes of n8n 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.1.0 |