2.15.1
7 years ago
4 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 Cleartext Storage of Sensitive Information in the process that handles Google Service Account credentials, where the full PEM private key is placed in the JWT header's Note: This is only exploitable if Google Service Account credentials are configured. How to fix Cleartext Storage of Sensitive Information? Upgrade | <1.121.40>=2.0.0-rc.0 <2.29.7>=2.30.0 <2.30.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Time-of-check Time-of-use (TOCTOU) Race Condition via a race condition in the How to fix Time-of-check Time-of-use (TOCTOU) Race Condition? Upgrade | <1.121.40>=2.0.0-rc.0 <2.29.7>=2.30.0 <2.30.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Incorrect Authorization in the Note: This is only exploitable if a credential has "Allowed HTTP Request Domains" configured and is usable by non-owner users. How to fix Incorrect Authorization? Upgrade | <1.121.40>=2.0.0-rc.0 <2.29.7>=2.30.0 <2.30.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to External Control of File Name or Path via the How to fix External Control of File Name or Path? Upgrade | <1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Prototype Pollution via the Edit Fields (Set) process when output fields are assigned using dot-notation path setters without restricting field names. An attacker can corrupt a shared global in the main How to fix Prototype Pollution? Upgrade | <1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1 |
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 | <1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via improper handling of message fields in the Send Email node. An attacker can access arbitrary files or initiate unauthorized network requests by supplying crafted non-string input to the Note: This is only exploitable if a pre-existing active workflow with an unauthenticated webhook exists, valid SMTP credentials are configured on the Send Email node, and untrusted input is mapped directly into the text or HTML body field. How to fix Server-side Request Forgery (SSRF)? Upgrade | <1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.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 an authenticated user has rights to create and execute workflows using the How to fix Command Injection? Upgrade | <1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to SQL Injection in the Note: This is only exploitable if a workflow author embeds untrusted expression data in a raw SQL query. How to fix SQL Injection? Upgrade | <1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to SQL Injection via the How to fix SQL Injection? Upgrade | <1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to SQL Injection in the How to fix SQL Injection? Upgrade | <2.25.2>=2.26.0 <2.26.1 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to SQL Injection through the Workarounds
How to fix SQL Injection? Upgrade | <2.24.0 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Prototype Pollution via the Microsoft SQL node’s Workarounds
How to fix Prototype Pollution? Upgrade | <2.24.0 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Exposure of Data Element to Wrong Session via the Notes
Workarounds
How to fix Exposure of Data Element to Wrong Session? Upgrade | <2.25.2>=2.26.0 <2.26.5 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Improper Handling of Highly Compressed Data (Data Amplification) via the Decompress operation in the Compression node. An attacker can cause the process to terminate and disrupt all workflows by sending a specially crafted compressed archive to a public webhook workflow, leading to memory exhaustion. How to fix Improper Handling of Highly Compressed Data (Data Amplification)? Upgrade | <2.23.0 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the webhook verification endpoints in the Meta, WhatsApp and Microsoft Teams trigger nodes, where a query parameter is reflected into the HTTP response without proper sanitization or Content-Security-Policy headers. An attacker can execute arbitrary JavaScript in the context of a logged-in user's browser by convincing the user to visit a specially crafted URL. How to fix Cross-site Scripting (XSS)? Upgrade | <2.24.0 |
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 SQL Injection via the MySQL, PostgreSQL, and Microsoft SQL nodes due to improper escaping of identifier values. An attacker can execute arbitrary SQL commands by supplying specially crafted table or column names through node configuration parameters. How to fix SQL Injection? Upgrade | <2.4.0 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Exposure of Sensitive System Information to an Unauthorized Control Sphere due to insufficient restrictions in the How to fix Exposure of Sensitive System Information to an Unauthorized Control Sphere? Upgrade | <2.7.0 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Protection Mechanism Failure via the Python Code node. An attacker can execute arbitrary code outside the intended security boundary by leveraging authenticated access and enabling Task Runners with Python support. This is only exploitable if Task Runners are enabled ( How to fix Protection Mechanism Failure? Upgrade | <2.3.0 |
n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Remote Code Execution (RCE) due to insufficient isolation in the Python Code Node that uses Pyodide. An authenticated attacker with permissions to create or modify workflows can execute arbitrary commands on the host system by creating or modifying workflows with malicious code. How to fix Remote Code Execution (RCE)? Upgrade | >=1.0.0 <2.0.0-rc.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 |