n8n-workflow 1.120.18

Direct Vulnerabilities

Known vulnerabilities in the n8n-workflow 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 Arbitrary Code Injection n8n-workflow is a Workflow base code of n8n Affected versions of this package are vulnerable to Arbitrary Code Injection via crafted expressions using arrow functions in the `expression`. An attacker can execute arbitrary system commands by bypassing the intended sandbox restrictions. Note: This is only exploitable if the attacker is an authenticated user with permission to create or modify workflows. How to fix Arbitrary Code Injection? Upgrade `n8n-workflow` to version 2.31.3, 2.32.1 or higher.	<2.31.3>=2.32.0 <2.32.1
M Authorization Bypass Through User-Controlled Key n8n-workflow is a Workflow base code 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-workflow` to version 1.120.19, 2.27.2, 2.28.1 or higher.	<1.120.19>=2.0.0 <2.27.2>=2.28.0 <2.28.1
M Prototype Pollution n8n-workflow is a Workflow base code of n8n Affected versions of this package are vulnerable to Prototype Pollution via the `deepCopy` and `replaceCircularReferences` utilities in `utils.ts`. An attacker can inject crafted `__proto__`, `constructor`, or `prototype` fields in a public webhook payload that is copied into workflow data, causing those fields to be treated as normal values by downstream nodes. This can cause workflows to act on attacker-controlled data as if it were trusted input, leading to confused-deputy behavior, such as targeting unintended records or issuing outbound requests using the workflow owner’s credentials. Workarounds Avoid exposing public (unauthenticated) webhook workflows that pass incoming data through transform nodes into action nodes that use sensitive credentials or database operations; this limits the confused-deputy attack path from attacker-supplied webhook payloads. Limit workflow creation and editing permissions to fully trusted users only; this reduces the chance that an attacker can introduce or modify a workflow that combines a public webhook with sensitive downstream actions. How to fix Prototype Pollution? Upgrade `n8n-workflow` to version 2.25.2, 2.26.1 or higher.	<2.25.2>=2.26.0 <2.26.1
C Remote Code Execution (RCE) n8n-workflow is a Workflow base code 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 `n8n-workflow` to version 2.0.0-rc.1 or higher.	>=1.0.0 <2.0.0-rc.1

Vulnerability

Vulnerable Version

Arbitrary Code Injection

n8n-workflow is a Workflow base code of n8n

Affected versions of this package are vulnerable to Arbitrary Code Injection via crafted expressions using arrow functions in the expression. An attacker can execute arbitrary system commands by bypassing the intended sandbox restrictions.

Note: This is only exploitable if the attacker is an authenticated user with permission to create or modify workflows.

How to fix Arbitrary Code Injection?

Upgrade n8n-workflow to version 2.31.3, 2.32.1 or higher.

<2.31.3>=2.32.0 <2.32.1

Authorization Bypass Through User-Controlled Key

n8n-workflow is a Workflow base code 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-workflow to version 1.120.19, 2.27.2, 2.28.1 or higher.

<1.120.19>=2.0.0 <2.27.2>=2.28.0 <2.28.1

Prototype Pollution

n8n-workflow is a Workflow base code of n8n

Affected versions of this package are vulnerable to Prototype Pollution via the deepCopy and replaceCircularReferences utilities in utils.ts. An attacker can inject crafted __proto__, constructor, or prototype fields in a public webhook payload that is copied into workflow data, causing those fields to be treated as normal values by downstream nodes. This can cause workflows to act on attacker-controlled data as if it were trusted input, leading to confused-deputy behavior, such as targeting unintended records or issuing outbound requests using the workflow owner’s credentials.

Workarounds

Avoid exposing public (unauthenticated) webhook workflows that pass incoming data through transform nodes into action nodes that use sensitive credentials or database operations; this limits the confused-deputy attack path from attacker-supplied webhook payloads.
Limit workflow creation and editing permissions to fully trusted users only; this reduces the chance that an attacker can introduce or modify a workflow that combines a public webhook with sensitive downstream actions.

How to fix Prototype Pollution?

Upgrade n8n-workflow to version 2.25.2, 2.26.1 or higher.

<2.25.2>=2.26.0 <2.26.1

Remote Code Execution (RCE)

n8n-workflow is a Workflow base code 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 n8n-workflow to version 2.0.0-rc.1 or higher.

>=1.0.0 <2.0.0-rc.1

n8n-workflow@1.120.18

Workflow base code of n8n

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically