CVE-2026-45732: CWE-639: Authorization Bypass Through User-Controlled Key in n8n-io n8n
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.
AI Analysis
Technical Summary
CVE-2026-45732 is an authorization bypass vulnerability in the n8n workflow automation platform affecting OAuth1 and OAuth2 credential reconnect endpoints. The flaw arises because these endpoints authorize access using credential:read permission rather than the stricter credential:update permission. Consequently, an authenticated user with read-only access to a shared credential can initiate an OAuth reconnect flow and replace the stored token material with tokens bound to an external account they control. This allows the attacker to execute workflows under their OAuth identity, enabling data exfiltration to attacker-controlled services and persistent compromise of shared integrations. The issue affects n8n versions prior to 1.123.43, 2.22.1, and 2.20.7 and is resolved in these fixed versions.
Potential Impact
An attacker with authenticated read-only access to a shared credential can overwrite OAuth tokens with their own, causing workflows to execute with the attacker's OAuth identity. This leads to unauthorized data exfiltration and persistent takeover of shared integrations, compromising confidentiality and integrity of data and workflows relying on the affected credentials.
Mitigation Recommendations
This vulnerability is fixed in n8n versions 1.123.43, 2.22.1, and 2.20.7. Users should upgrade to these versions or later to remediate the issue. No vendor advisory content contradicts this; therefore, upgrading is the recommended mitigation.
CVE-2026-45732: CWE-639: Authorization Bypass Through User-Controlled Key in n8n-io n8n
Description
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.
CVSS v4.0
Score 8.3high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-45732 is an authorization bypass vulnerability in the n8n workflow automation platform affecting OAuth1 and OAuth2 credential reconnect endpoints. The flaw arises because these endpoints authorize access using credential:read permission rather than the stricter credential:update permission. Consequently, an authenticated user with read-only access to a shared credential can initiate an OAuth reconnect flow and replace the stored token material with tokens bound to an external account they control. This allows the attacker to execute workflows under their OAuth identity, enabling data exfiltration to attacker-controlled services and persistent compromise of shared integrations. The issue affects n8n versions prior to 1.123.43, 2.22.1, and 2.20.7 and is resolved in these fixed versions.
Potential Impact
An attacker with authenticated read-only access to a shared credential can overwrite OAuth tokens with their own, causing workflows to execute with the attacker's OAuth identity. This leads to unauthorized data exfiltration and persistent takeover of shared integrations, compromising confidentiality and integrity of data and workflows relying on the affected credentials.
Mitigation Recommendations
This vulnerability is fixed in n8n versions 1.123.43, 2.22.1, and 2.20.7. Users should upgrade to these versions or later to remediate the issue. No vendor advisory content contradicts this; therefore, upgrading is the recommended mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-13T05:51:48.667Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3ab6d9eed863c81e4f9e91
Added to database: 06/23/2026, 16:39:53 UTC
Last enriched: 06/30/2026, 22:56:17 UTC
Last updated: 08/05/2026, 12:41:15 UTC
Views: 80
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.