CVE-2026-45732
OAuth reconnect lets a read-only user overwrite tokens, enabling data exfiltration.
Is CVE-2026-45732 being exploited?
Not confirmed. CVE-2026-45732 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-45732?
CVE-2026-45732 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-45732?
Yes. A fix has been recorded for CVE-2026-45732. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-45732 affect?
CVE-2026-45732 affects n8n platform (self-hosted & cloud), Versions prior to 1.123.43, 2.22.1, 2.20.7. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-45732?
Upgrade to patched versions (1.123.43, 2.22.1, 2.20.7+).
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated user with credential:read can hijack OAuth tokens via reconnect flow, causing workflows to run under attacker identity and exfiltrate data.
Patch when possible
- affected< 1.123.43
- affected>= 2.0.0-rc.0 and < 2.20.7
- affected>= 2.21.0 and < 2.21.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.