Skip to main content
VulnerabilityPublished Updated

CVE-2026-45732: n8n · Insecure Direct Object Reference

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High · fixed in 2.21.1 : patch n8n soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.21.1, 2.20.7, 1.123.43 +1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade n8n to 2.21.1, 2.20.7 or 1.123.43; n8n-io/n8n to 2.22.1, 2.20.7 or 1.123.43.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • >=2.21.0 <2.21.1
Fixed in
  • 2.21.1
n8n-ion8nAffected
  • >=2.0.0-rc.0 <2.20.7
Fixed in
  • 2.20.7
n8n-ion8nAffected
  • <1.123.43
Fixed in
  • 1.123.43
npmn8n-io/n8npkg:npm/n8n-io/n8nOther threatsAffected
  • <1.123.43
  • <2.22.1
  • <2.20.7
Fixed in
  • 1.123.43
  • 2.22.1
  • 2.20.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in n8n versions 1.123.43, 2.22.1, and 2.20.7. Users should upgrade to these versions or later to remediate the issue. No vendor advisory content contradicts this; therefore, upgrading is the recommended mitigation.

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.

References

Community reviews

Loading reviews…