Advisoriesby Ibisn8n Has a 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....
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | < 1.123.43 | 1.123.43 |
| >= 2.21.0, < 2.21.1 | 2.21.1 | |
| >= 2.0.0-rc.0, < 2.20.7 | 2.20.7 |
Details and references
## 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
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-639
- Also known as
- CVE-2026-45732
More n8n advisories
All n8n
n8n: Credential exfiltration via Allowed HTTP Request Domains BypassCVE-2026-56348fixed in 2.20.0n8n: Legacy ExecuteWorkflow Node Bypassed File Path RestrictionsCVE-2026-56352fixed in 2.19.3n8n Has a Source Control Pull SQL InjectionCVE-2026-44792fixed in 1.123.43 +2n8n Has an XML Node Prototype Pollution Patch BypassCVE-2026-44791fixed in 1.123.43 +2n8n Has an Arbitrary File Read via Git NodeCVE-2026-44790fixed in 1.123.43 +2n8n: HTTP Request Node Pagination Prototype Pollution to RCECVE-2026-44789fixed in 1.123.43 +2