CVE-2026-65595
n8n Token Exchange flaw grants admin API scopes, enabling privilege escalation and possible RCE.
Is CVE-2026-65595 being exploited?
Not confirmed. CVE-2026-65595 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.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-65595?
CVE-2026-65595 is rated High with a CVSS score of 8.9. 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-65595?
Yes. A fix has been recorded for CVE-2026-65595. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65595 affect?
CVE-2026-65595 affects n8n versions before 2.30.1 and 2.29.8, Token Exchange module enabled, Public API enabled, Unverified Community Package install enabled (for RCE). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65595?
Upgrade to n8n 2.30.1 or 2.29.8+; or disable Token Exchange, Public API, and unverified package installs until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Low-privileged users with a trusted external JWT can gain admin API access: role escalation, user create/delete; RCE possible if unverified package installs enabled.
Immediate action required
- affected< 2.30.1
- affected< 2.29.8
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.