CVE-2026-65595: n8n privilege escalation in Token Exchange module

CVE-2026-65595 · Severity: high · CVSS 4 · Published 2026-07-22

n8n is a workflow automation tool used to connect various business applications. A vulnerability in its token exchange system allows low-privileged users to gain full administrative control over the platform. An attacker could use this access to create or delete users, escalate their own permissions, and potentially execute unauthorized code, leading to a complete compromise of the automation environment and its connected data.

Technologies: N8n, n8n (npm). Vendors: N8n, npm.

Quick answers

Is CVE-2026-65595 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-65595 being exploited in the wild.
How severe is CVE-2026-65595?
High severity, with a CVSS score of 4, published 22 July 2026.
Which products and versions are affected?
N8n < 2.30.1, < 2.29.8, >= 2.30.0, < 2.30.1; < 2.29.8; n8n (npm) SEMVER:introduced=2.30.0,fixed=2.30.1.
Is there a fix for CVE-2026-65595?
Yes. n8n (npm): upgrade to 2.30.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-65595 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-65595?
Check whether you run N8n or n8n (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • n8n (npm): upgrade to 2.30.1 or later
    npm install n8n@2.30.1

Technical details

A privilege management vulnerability (CWE-269) exists in n8n's Token Exchange module where JWTs are incorrectly assigned all Public API key scopes regardless of the user's actual role. An attacker with low-privileged access who can obtain a valid external JWT trusted by a configured issuer can exchange it for an access token with full administrative rights. This allows for unauthorized operations such as role escalation, user management, and, if community packages are enabled, remote code execution. The vulnerability requires N8N_TOKEN_EXCHANGE_ENABLED and the Public API to be active. It is patched in versions 2.30.1 and 2.29.8.

Affected products

  • n8n-io n8n >= 2.30.0, < 2.30.1; < 2.29.8

Identifiers

  • CVE-2026-65595
  • GHSA-777w-rpr6-c52h

Timeline

  • 2026-07-08: disclosed: Initial disclosure by reporter
  • 2026-07-22: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.