CVE-2026-65595: Privilege Escalation in n8n Token Exchange
- Vendor
- N8n
CVE-2026-65595 is a privilege escalation vulnerability in n8n affecting versions before 2.30.1 and before 2.29.8 on the affected maintenance branch. The flaw is caused by incorrect privilege handling in the Token Exchange module: JWTs issued through Token Exchange are assigned all Public API key scopes regardless of the acting user's actual role. On deployments where both Token Exchange and the Public API are enabled, a low-privileged user who can obtain a valid external JWT trusted by a configured issuer can exchange it for an access token that is over-scoped and accepted for administrator-only Public API operations. Exposed actions include administrative user management functions such as user creation, user deletion, and role escalation. In configurations that also permit installation of unverified Community Packages, the privilege escalation can be chained into remote code execution.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows a low-privileged authenticated user to bypass intended role restrictions and perform administrator-only actions through the Public API. This can result in unauthorized account creation and deletion, privilege escalation to higher roles, and full administrative control over affected n8n functionality exposed through the API. Where unverified Community Package installation is enabled, the attacker can further leverage the elevated privileges to achieve remote code execution on the n8n instance. The vulnerability therefore impacts confidentiality, integrity, and availability and can lead to complete compromise of the application environment.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, disable the Token Exchange feature. If Token Exchange must remain enabled, restrict Public API exposure to trusted clients and trusted network paths only, and minimize which external issuers are trusted for JWT exchange. Disable unverified Community Package installation to remove the remote code execution path. Review and reduce user privileges where possible, especially for accounts capable of obtaining externally trusted JWTs. These measures reduce exposure but do not fully remediate the underlying flaw.
Remediation
Patch, then assume compromise.
Upgrade n8n to a fixed release. The issue is addressed in version 2.30.1 and 2.29.8 for the affected branches; organizations should deploy the appropriate patched version or a later release. After upgrading, review Token Exchange and Public API configuration, validate that externally trusted JWT issuers are still required and correctly scoped, and audit user roles and administrative actions for signs of misuse prior to remediation.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-65595 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-65595 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-65595?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-65595.
- Is there a patch for CVE-2026-65595?
- Upgrade n8n to a fixed release. The issue is addressed in version 2.30.1 and 2.29.8 for the affected branches; organizations should deploy the appropriate patched version or a later release.
- What products are affected by CVE-2026-65595?
- N8n.
- How severe is CVE-2026-65595?
- CVE-2026-65595 has a CVSS v4 score of 8.9 (High) and an EPSS score of 0.69% (53rd percentile) as of Sep 25, 2026.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.