n8n-io n8n up to 1.123.42/2.20.6/2.21.0 OAuth2 Credential authorization

Summaryinfo

A vulnerability was found in n8n-io n8n up to 1.123.42/2.20.6/2.21.0. It has been rated as critical. This issue affects some unknown processing of the component OAuth2 Credential Handler. Performing a manipulation results in authorization. This vulnerability is identified as CVE-2026-45732. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, was found in n8n-io n8n up to 1.123.42/2.20.6/2.21.0. This affects an unknown function of the component OAuth2 Credential Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

n8n is an open source workflow automation platform. Prior to 1.123.43, 2.22.1, and 2.20.7, the OAuth1 and OAuth2 credential reconnect endpoints authorized access using credential:read rather than credential:update. An authenticated user with read-only access to a shared credential could initiate an OAuth reconnect flow and overwrite the stored token material for that credential with tokens bound to an external account they control. Workflows relying on the affected credential would subsequently execute under the attacker's OAuth identity, enabling data exfiltration to attacker-controlled external services and persistent takeover of shared integrations. This vulnerability is fixed in 1.123.43, 2.22.1, and 2.20.7.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-45732 since 05/13/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.123.43, 2.20.7 or 2.21.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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
• 1.123.33
• 1.123.34
• 1.123.35
• 1.123.36
• 1.123.37
• 1.123.38
• 1.123.39
• 1.123.40
• 1.123.41
• 1.123.42
• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.20.0
• 2.20.1
• 2.20.2
• 2.20.3
• 2.20.4
• 2.20.5
• 2.20.6
• 2.21.0

Website

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

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion