CVE-2026-45732: n8n: Cross-user Authorization Bypass in Dynamic Credential OAuth Endpoints
Impact 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 issue affects instances where credentials are shared with other users or across projects.
Patches The issue has been fixed in n8n versions 1.123.43, 2.20.7, and 2.21.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict credential sharing to fully trusted users only. - Audit shared credentials for unexpected OAuth token changes and revoke any tokens that may have been replaced.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
--- n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.20.7 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.21.1 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 1.123.43 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.43 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.22.1 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.20.7 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.21.1 - Configuration
Restrict credential sharing so it is only available to fully trusted users (avoid sharing with other users or across projects).
Credential sharing / access control Restrict credential sharing to fully trusted users only = fully trusted users only - Operational
Audit shared credentials for unexpected OAuth token changes and revoke any tokens that may have been replaced.
Event History
Frequently Asked Questions
What is the impact of CVE-2026-45732?
CVE-2026-45732 allows authenticated users with read-only access to overwrite stored OAuth tokens via credential reconnect endpoints.
Which versions of n8n are affected by CVE-2026-45732?
CVE-2026-45732 affects n8n versions from 2.0.0-rc.0 up to 2.20.7, 2.21.0 specifically, and all versions prior to 1.123.43.
How can I remediate CVE-2026-45732?
To address CVE-2026-45732, you should upgrade n8n to version 2.20.8, 2.21.1 or later, or 1.123.43.
What type of vulnerability is CVE-2026-45732?
CVE-2026-45732 is a security vulnerability related to improper authorization in OAuth credential management.
Who is affected by CVE-2026-45732?
CVE-2026-45732 mainly affects users of n8n who utilize OAuth authentication with shared credentials.