n8n-nodes-base 2.27.3

Direct Vulnerabilities

Known vulnerabilities in the n8n-nodes-base 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 Cleartext Storage of Sensitive Information 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 `kid` field instead of a key identifier. An attacker can gain unauthorized access to Google Cloud resources by recovering the private key from Base64-encoded JWT headers that are logged or inspected. Note: This is only exploitable if Google Service Account credentials are configured. How to fix Cleartext Storage of Sensitive Information? Upgrade `n8n-nodes-base` to version 1.121.40, 2.29.7, 2.30.1 or higher.	<1.121.40>=2.0.0-rc.0 <2.29.7>=2.30.0 <2.30.1
H Time-of-check Time-of-use (TOCTOU) Race Condition 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 `clone` action. An attacker can execute arbitrary code on the server by exploiting a time-of-check to time-of-use (TOCTOU) issue, swapping a directory for a symlink after path validation but before the clone operation, which results in a crafted repository being loaded and executed as a custom node on the next restart. How to fix Time-of-check Time-of-use (TOCTOU) Race Condition? Upgrade `n8n-nodes-base` to version 1.121.40, 2.29.7, 2.30.1 or higher.	<1.121.40>=2.0.0-rc.0 <2.29.7>=2.30.0 <2.30.1
M Incorrect Authorization n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Incorrect Authorization in the `GraphQL` node when the "Allowed HTTP Request Domains" restriction is not enforced on HTTP-based credentials. An attacker can access restricted credentials by configuring the node's endpoint to send requests to a server under their control. 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 `n8n-nodes-base` to version 1.121.40, 2.29.7, 2.30.1 or higher.	<1.121.40>=2.0.0-rc.0 <2.29.7>=2.30.0 <2.30.1
H External Control of File Name or Path 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 `Edit Image`. An attacker can write arbitrary files outside the intended directory by supplying crafted values to the output format parameter. How to fix External Control of File Name or Path? Upgrade `n8n-nodes-base` to version 1.121.42, 2.31.3, 2.32.1 or higher.	<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1
H Prototype Pollution 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 `Node.js` by naming a field after an inherited built-in method path, which causes all authenticated requests to fail and results in a denial of service for all users until the process is restarted. How to fix Prototype Pollution? Upgrade `n8n-nodes-base` to version 1.121.42, 2.31.3, 2.32.1 or higher.	<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1
H Directory Traversal n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Directory Traversal via the `Git` node's fetch, pull, or push-tags operations. An attacker can access files and history outside the intended workspace by configuring an allowlisted remote value to point to a local path beyond the sandbox. How to fix Directory Traversal? Upgrade `n8n-nodes-base` to version 1.121.42, 2.31.3, 2.32.1 or higher.	<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1
H Server-side Request Forgery (SSRF) 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 `text` or `HTML` body fields. 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 `n8n-nodes-base` to version 1.121.42, 2.31.3, 2.32.1 or higher.	<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1
H Command Injection n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Command Injection via the `Git` node. An attacker can execute arbitrary commands as the application process user by crafting a local repository to trigger `git` hooks during workflow execution. Note: This is only exploitable if an authenticated user has rights to create and execute workflows using the `Git` node under default `git` security settings. How to fix Command Injection? Upgrade `n8n-nodes-base` to version 1.121.42, 2.31.3, 2.32.1 or higher.	<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1
H SQL Injection n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to SQL Injection in the `executeQuery`. An attacker can execute arbitrary SQL commands by injecting untrusted expression data directly into a raw SQL query string. Note: This is only exploitable if a workflow author embeds untrusted expression data in a raw SQL query. How to fix SQL Injection? Upgrade `n8n-nodes-base` to version 1.121.42, 2.31.3, 2.32.1 or higher.	<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1
H SQL Injection n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to SQL Injection via the `PostgresTrigger`. An attacker can execute arbitrary SQL commands on the connected PostgreSQL database by supplying crafted input to identifier parameters, leading to full read and write access with the configured credential's privileges. How to fix SQL Injection? Upgrade `n8n-nodes-base` to version 1.121.42, 2.31.3, 2.32.1 or higher.	<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1
M Authorization Bypass Through User-Controlled Key n8n-nodes-base is a Base nodes of n8n Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key via a mismatch between static validation and the runtime expression engine in external secrets handling. An attacker can access unauthorized secret values by embedding external secret references into credentials that bypass static validation, which are then resolved during workflow execution. Note: This is only exploitable if an external secrets provider is configured and Advanced Permissions are enabled. How to fix Authorization Bypass Through User-Controlled Key? Upgrade `n8n-nodes-base` to version 1.121.38, 2.27.4, 2.28.1 or higher.	<1.121.38>=2.0.0 <2.27.4>=2.28.0 <2.28.1
H Command Injection n8n-nodes-base is a Base nodes of n8n 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-nodes-base`.	>=0.1.0

Vulnerability

Vulnerable Version

Cleartext Storage of Sensitive Information

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 kid field instead of a key identifier. An attacker can gain unauthorized access to Google Cloud resources by recovering the private key from Base64-encoded JWT headers that are logged or inspected.

Note: This is only exploitable if Google Service Account credentials are configured.

How to fix Cleartext Storage of Sensitive Information?

Upgrade n8n-nodes-base to version 1.121.40, 2.29.7, 2.30.1 or higher.

<1.121.40>=2.0.0-rc.0 <2.29.7>=2.30.0 <2.30.1

Time-of-check Time-of-use (TOCTOU) Race Condition

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 clone action. An attacker can execute arbitrary code on the server by exploiting a time-of-check to time-of-use (TOCTOU) issue, swapping a directory for a symlink after path validation but before the clone operation, which results in a crafted repository being loaded and executed as a custom node on the next restart.

How to fix Time-of-check Time-of-use (TOCTOU) Race Condition?

Upgrade n8n-nodes-base to version 1.121.40, 2.29.7, 2.30.1 or higher.

<1.121.40>=2.0.0-rc.0 <2.29.7>=2.30.0 <2.30.1

Incorrect Authorization

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Incorrect Authorization in the GraphQL node when the "Allowed HTTP Request Domains" restriction is not enforced on HTTP-based credentials. An attacker can access restricted credentials by configuring the node's endpoint to send requests to a server under their control.

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 n8n-nodes-base to version 1.121.40, 2.29.7, 2.30.1 or higher.

<1.121.40>=2.0.0-rc.0 <2.29.7>=2.30.0 <2.30.1

External Control of File Name or Path

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 Edit Image. An attacker can write arbitrary files outside the intended directory by supplying crafted values to the output format parameter.

How to fix External Control of File Name or Path?

Upgrade n8n-nodes-base to version 1.121.42, 2.31.3, 2.32.1 or higher.

<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1

Prototype Pollution

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 Node.js by naming a field after an inherited built-in method path, which causes all authenticated requests to fail and results in a denial of service for all users until the process is restarted.

How to fix Prototype Pollution?

Upgrade n8n-nodes-base to version 1.121.42, 2.31.3, 2.32.1 or higher.

<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1

Directory Traversal

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Directory Traversal via the Git node's fetch, pull, or push-tags operations. An attacker can access files and history outside the intended workspace by configuring an allowlisted remote value to point to a local path beyond the sandbox.

How to fix Directory Traversal?

Upgrade n8n-nodes-base to version 1.121.42, 2.31.3, 2.32.1 or higher.

<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1

Server-side Request Forgery (SSRF)

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 text or HTML body fields.

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 n8n-nodes-base to version 1.121.42, 2.31.3, 2.32.1 or higher.

<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1

Command Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Command Injection via the Git node. An attacker can execute arbitrary commands as the application process user by crafting a local repository to trigger git hooks during workflow execution.

Note: This is only exploitable if an authenticated user has rights to create and execute workflows using the Git node under default git security settings.

How to fix Command Injection?

Upgrade n8n-nodes-base to version 1.121.42, 2.31.3, 2.32.1 or higher.

<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1

SQL Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to SQL Injection in the executeQuery. An attacker can execute arbitrary SQL commands by injecting untrusted expression data directly into a raw SQL query string.

Note: This is only exploitable if a workflow author embeds untrusted expression data in a raw SQL query.

How to fix SQL Injection?

Upgrade n8n-nodes-base to version 1.121.42, 2.31.3, 2.32.1 or higher.

<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1

SQL Injection

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to SQL Injection via the PostgresTrigger. An attacker can execute arbitrary SQL commands on the connected PostgreSQL database by supplying crafted input to identifier parameters, leading to full read and write access with the configured credential's privileges.

How to fix SQL Injection?

Upgrade n8n-nodes-base to version 1.121.42, 2.31.3, 2.32.1 or higher.

<1.121.42>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1

Authorization Bypass Through User-Controlled Key

n8n-nodes-base is a Base nodes of n8n

Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key via a mismatch between static validation and the runtime expression engine in external secrets handling. An attacker can access unauthorized secret values by embedding external secret references into credentials that bypass static validation, which are then resolved during workflow execution.

Note: This is only exploitable if an external secrets provider is configured and Advanced Permissions are enabled.

How to fix Authorization Bypass Through User-Controlled Key?

Upgrade n8n-nodes-base to version 1.121.38, 2.27.4, 2.28.1 or higher.

<1.121.38>=2.0.0 <2.27.4>=2.28.0 <2.28.1

Command Injection

n8n-nodes-base is a Base nodes of n8n

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-nodes-base.

>=0.1.0

n8n-nodes-base@2.27.3

Base nodes of n8n

latest version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically