SA-26-213 High

n8n: n8n Has a Cross-user Authorization Bypass in Dynamic Credential OAuth Endpoints

n8n

Severity
High, CVSS 8.1
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Record
CVE-2026-45732
Affects
n8n
Known exploited
Not listed in the CISA Known Exploited Vulnerabilities catalog
Published
Record first published by the source
June 23, 2026
Source last modified
October 26, 2026

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.

Description quoted from the NVD record.

Who is affected

n8n is a tool for automating tasks by linking different apps and online services together in workflows. This flaw affects versions before 1.123.43, 2.22.1 and 2.20.7, in the feature that reconnects saved account logins (credentials) to outside services. A signed-in user who was only allowed to view a shared saved login could reconnect it to an outside account they control. Workflows using that login would then run under the attacker's account, which could let them send your data to their own services and keep control of shared connections. This flaw is rated High.

What to do

  1. Find out who looks after n8n for your organization: the person who installed and runs it, or an IT provider or vendor who manages it for you.
  2. If your organization runs n8n itself, that person should update it to a fixed version: 1.123.43, 2.22.1 or 2.20.7, choosing the one that matches the version line you already use.
  3. If an IT provider or vendor runs n8n for you, send them this advisory and ask when the update will be done.

Analysis written from the source record as of October 26, 2026 and reviewed before publishing.

Sources

MORE ADVISORIES

See all