n8n-core 1.122.34

Direct Vulnerabilities

Known vulnerabilities in the n8n-core 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
M Prototype Pollution n8n-core is a Core functionality of n8n Affected versions of this package are vulnerable to Prototype Pollution in the `expression engine`. An attacker can cause the application to become unresponsive or crash by manipulating array-element access to obtain a reference to a host built-in and pollute its prototype in the main process. Note: This is only exploitable if the VM expression engine is enabled and the attacker is an authenticated user able to create or edit workflow expressions. How to fix Prototype Pollution? Upgrade `n8n-core` to version 1.122.38, 2.31.3, 2.32.1 or higher.	<1.122.38>=2.0.0-rc.0 <2.31.3>=2.32.0 <2.32.1
M Authorization Bypass Through User-Controlled Key n8n-core is a Core functionality 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-core` to version 1.122.35, 2.27.3, 2.28.1 or higher.	<1.122.35>=2.0.0 <2.27.3>=2.28.0 <2.28.1
H Insufficiently Protected Credentials n8n-core is a Core functionality of n8n Affected versions of this package are vulnerable to Insufficiently Protected Credentials through the HTTP Request V3 pagination expression handling in `packages/nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts` and `packages/core/src/execution-engine/node-execution-context/utils/request-helpers/pagination.ts`. An authenticated user with access to a shared workflow can read credential-populated request headers by supplying a pagination expression that accesses `$request.headers`. When an HTTP Request node uses HTTP Header Auth credentials and pagination is enabled, the expression engine exposes the live request object with the secret-bearing headers attached. The attacker can copy that secret into item data and exfiltrate it through later workflow steps, exposing shared credentials to unauthorized workflow editors. Notes This only applies when `N8N_EXPRESSION_ENGINE=vm` is set; the advisory’s leak path depends on the VM-based expression runtime exposing `$request` during pagination evaluation. The affected workflow must use HTTP Header Auth on the paginated request; the secret shown in `$request.headers` comes from credential-populated request headers, not from ordinary request data. Workarounds Restrict workflow sharing to fully trusted users only. Avoid sharing credentials with use-only access to untrusted users on workflows that use HTTP Request nodes with pagination enabled. How to fix Insufficiently Protected Credentials? Upgrade `n8n-core` to version 1.122.35, 2.27.3, 2.28.1 or higher.	<1.122.35>=2.0.0-rc.0 <2.27.3>=2.28.0 <2.28.1
M Server-side Request Forgery (SSRF) n8n-core is a Core functionality of n8n Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the `POST /rest/dynamic-node-parameters/options` endpoint. An attacker can redirect responses to a server under their control by sending a specially crafted request with `loadOptions.routing.request.url` set to another host. How to fix Server-side Request Forgery (SSRF)? Upgrade `n8n-core` to version 2.20.0 or higher.	<2.20.0

Vulnerability

Vulnerable Version

Prototype Pollution

n8n-core is a Core functionality of n8n

Affected versions of this package are vulnerable to Prototype Pollution in the expression engine. An attacker can cause the application to become unresponsive or crash by manipulating array-element access to obtain a reference to a host built-in and pollute its prototype in the main process.

Note: This is only exploitable if the VM expression engine is enabled and the attacker is an authenticated user able to create or edit workflow expressions.

How to fix Prototype Pollution?

Upgrade n8n-core to version 1.122.38, 2.31.3, 2.32.1 or higher.

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

Authorization Bypass Through User-Controlled Key

n8n-core is a Core functionality 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-core to version 1.122.35, 2.27.3, 2.28.1 or higher.

<1.122.35>=2.0.0 <2.27.3>=2.28.0 <2.28.1

Insufficiently Protected Credentials

n8n-core is a Core functionality of n8n

Affected versions of this package are vulnerable to Insufficiently Protected Credentials through the HTTP Request V3 pagination expression handling in packages/nodes-base/nodes/HttpRequest/V3/HttpRequestV3.node.ts and packages/core/src/execution-engine/node-execution-context/utils/request-helpers/pagination.ts. An authenticated user with access to a shared workflow can read credential-populated request headers by supplying a pagination expression that accesses $request.headers. When an HTTP Request node uses HTTP Header Auth credentials and pagination is enabled, the expression engine exposes the live request object with the secret-bearing headers attached. The attacker can copy that secret into item data and exfiltrate it through later workflow steps, exposing shared credentials to unauthorized workflow editors.

Notes

This only applies when N8N_EXPRESSION_ENGINE=vm is set; the advisory’s leak path depends on the VM-based expression runtime exposing $request during pagination evaluation.
The affected workflow must use HTTP Header Auth on the paginated request; the secret shown in $request.headers comes from credential-populated request headers, not from ordinary request data.

Workarounds

Restrict workflow sharing to fully trusted users only.
Avoid sharing credentials with use-only access to untrusted users on workflows that use HTTP Request nodes with pagination enabled.

How to fix Insufficiently Protected Credentials?

Upgrade n8n-core to version 1.122.35, 2.27.3, 2.28.1 or higher.

<1.122.35>=2.0.0-rc.0 <2.27.3>=2.28.0 <2.28.1

Server-side Request Forgery (SSRF)

n8n-core is a Core functionality of n8n

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the POST /rest/dynamic-node-parameters/options endpoint. An attacker can redirect responses to a server under their control by sending a specially crafted request with loadOptions.routing.request.url set to another host.

How to fix Server-side Request Forgery (SSRF)?

Upgrade n8n-core to version 2.20.0 or higher.

<2.20.0

n8n-core@1.122.34

Core functionality of n8n

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically