CVE-2026-45732
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedn8n 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe OAuth1 and OAuth2 credential reconnect endpoints in n8n incorrectly authorized access using the credential:read permission instead of credential:update. This allowed authenticated users with read-only access to shared credentials to initiate OAuth reconnect flows and replace stored token material with tokens bound to attacker-controlled external accounts, causing workflows to execute under the attacker's OAuth identity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.123.43>= 2.0.0, < 2.20.7>= 2.21.0, < 2.22.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed n8n versionRun 'n8n --version' from command line, or check the version field in package.json within the n8n installation directory, or query the n8n API endpoint /rest/versionAffected if The version falls outside the fixed versions: not 1.123.43+, not 2.20.7+, not 2.22.1+ (for 2.21.x and later)
-
Determine if credentials are shared with read-only accessReview the n8n UI under Settings > Credentials > Share or query the credentials table in the database for entries where 'share_role' or equivalent indicates read-only (viewer) access granted to other usersAffected if Any credentials are shared with users who only have read (not update) permissions
-
Review audit logs for OAuth reconnect activityExamine n8n audit logs (typically in /home/node/.n8n/logs/ or configured log directory) for entries containing 'reconnect' or 'oauth' actions on credentials, noting the user account performing each actionAffected if Reconnect actions were performed by users who only had read-only access to the affected credentials
-
Check for unexpected credential owner changesCompare the current owner of shared credentials against known legitimate owners by querying the credentials table or reviewing credential history in the UIAffected if Any shared credentials show ownership or binding changes that were not initiated by users with update permission
You are affected if your n8n version is below 1.123.43, below 2.20.7 (for 2.0.0-2.20.x), or below 2.22.1 (for 2.21.x-2.22.0) AND you have credentials shared with read-only users who may have initiated OAuth reconnect flows.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.123.432.20.72.22.1
Upgrade to n8n versions 1.123.43, 2.22.1, or 2.20.7. Additionally, audit shared credential permissions and investigate any suspicious OAuth reconnection events that may indicate active exploitation.
Upgrade to n8n 1.123.43 (for 1.x) or 2.20.7/2.22.1 (for 2.x) depending on your current branch
- Identify your current n8n version by checking the running instance or your deployment configuration
- Determine which branch (1.x or 2.x) you are currently using
- For 1.x users: Upgrade to version 1.123.43 or later
- For 2.x users (< 2.21.0): Upgrade to version 2.20.7
- For 2.x users (>= 2.21.0): Upgrade to version 2.22.1
- Backup your n8n database before performing the upgrade
- Follow your deployment method's upgrade procedure (Docker, npm, or binary)
- After upgrade, verify the n8n instance is running correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45732 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data