n8n-io n8n up to 1.123.32/2.17.4 authorization

Summaryinfo

A vulnerability described as critical has been identified in n8n-io n8n up to 1.123.32/2.17.4. The impacted element is an unknown function. Such manipulation leads to authorization. This vulnerability is documented as CVE-2026-42226. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in n8n-io n8n up to 1.123.32/2.17.4. It has been rated as critical. Affected by this issue is an unknown code block. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. CVE summarizes:

n8n is an open source workflow automation platform. Prior to versions 1.123.33 and 2.17.5, the dynamic-node-parameters endpoints did not verify whether the authenticated caller was authorized to use a supplied credential reference. An authenticated user with access to a shared workflow could supply a foreign credential ID in the request body, causing the backend to decrypt and use that credential in a helper execution path where the caller also controls the destination URL. This allowed the caller to force the backend to authenticate against attacker-controlled infrastructure using a credential belonging to another user, effectively exfiltrating a reusable API key. The issue is not limited to any single node type; any node that resolves credentials dynamically through these endpoints may be affected. This issue has been patched in versions 1.123.33, 2.17.5, and 2.18.0.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-42226 since 04/25/2026. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available.

Upgrading to version 1.123.33 or 2.17.5 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-27093). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

• n8n-io

Name

• n8n

Version

• 1.123.0
• 1.123.1
• 1.123.2
• 1.123.3
• 1.123.4
• 1.123.5
• 1.123.6
• 1.123.7
• 1.123.8
• 1.123.9
• 1.123.10
• 1.123.11
• 1.123.12
• 1.123.13
• 1.123.14
• 1.123.15
• 1.123.16
• 1.123.17
• 1.123.18
• 1.123.19
• 1.123.20
• 1.123.21
• 1.123.22
• 1.123.23
• 1.123.24
• 1.123.25
• 1.123.26
• 1.123.27
• 1.123.28
• 1.123.29
• 1.123.30
• 1.123.31
• 1.123.32
• 2.17.0
• 2.17.1
• 2.17.2
• 2.17.3
• 2.17.4

Website

• Product: https://github.com/n8n-io/n8n/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion