CVE-2026-45732: n8n: Cross-user Authorization Bypass in Dynamic Credential OAuth Endpoints

Published May 14, 2026
·
Updated

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

6 affected componentsFixes available
npm/n8n>=2.0.0-rc.0<2.20.7
2.20.7
npm/n8n>=2.21.0<2.21.1
2.21.1
npm/n8n<1.123.43
1.123.43
n8n N8n Node.js<1.123.43
n8n N8n Node.js>=2.0.0<2.20.7
n8n N8n Node.js>=2.21.0<2.22.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.20.7
  2. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.21.1
  3. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.123.43
  4. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 1.123.43
  5. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.22.1
  6. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.20.7
  7. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.21.1
  8. 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
  9. Operational

    Audit shared credentials for unexpected OAuth token changes and revoke any tokens that may have been replaced.

Event History

May 14, 2026
Advisory Published
via GitHub·04:18 PM
Data Sourced
via GitHub·04:18 PM
DescriptionWeaknessAffected Software
Jun 23, 2026
CVE Published
via MITRE·03:52 PM
Data Sourced
via MITRE·03:52 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

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.

2

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.

3

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.

4

What type of vulnerability is CVE-2026-45732?

CVE-2026-45732 is a security vulnerability related to improper authorization in OAuth credential management.

5

Who is affected by CVE-2026-45732?

CVE-2026-45732 mainly affects users of n8n who utilize OAuth authentication with shared credentials.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203