Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
8.9
CVE-2026-65595: n8n Public API Key Privilege Escalation via Token Exchange
CVE-2026-65595
CVE-2026-65595
GHSA-777w-rpr6-c52h
GHSA-777w-rpr6-c52h
Summary
A low-privileged user can gain elevated access to n8n's Public API, potentially allowing them to create, delete, or escalate user roles. This can happen if a malicious user obtains a valid external token that n8n trusts. To mitigate this, update n8n to version 2.30.1 or later.
What to do
- Update GitHub Actions n8n to version 2.30.1.
- Update GitHub Actions n8n to version 2.29.8.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | n8n-io | n8n |
< 2.30.1 < 2.29.8 |
| npm | GitHub Actions | n8n |
>= 2.30.0, < 2.30.1 < 2.29.8 Fix: upgrade to 2.30.1
|
Original title
n8n: Privilege Escalation and Code Execution via Full Public API Key Scope Assignment to Token Exchange JWTs
Original description
## Impact
JWTs issued through the Token Exchange module were assigned all Public API key scopes, regardless of the acting user's actual role. A low-privileged user who could obtain a valid external JWT trusted by a configured issuer could therefore use the resulting access token to invoke administrator-only Public API operations, such as role escalation, user creation, and user deletion.
The issue only affects instances where the Token Exchange feature and the Public API are enabled (N8N_TOKEN_EXCHANGE_ENABLED=true, N8N_ENV_FEAT_TOKEN_EXCHANGE=true) and the attacker can obtain an external JWT accepted by a configured trusted key. Role escalation additionally requires an Advanced Permissions license; Community Package installation additionally requires `N8N_COMMUNITY_PACKAGES_ENABLED=true` and `N8N_UNVERIFIED_PACKAGES_ENABLED=true`.
## Patches
The issue has been fixed in n8n version 2.30.1 and 2.29.8. Users should upgrade to this version or later to remediate the vulnerability.
## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Disable the Token Exchange feature by setting `N8N_TOKEN_EXCHANGE_ENABLED=false` or `N8N_ENV_FEAT_TOKEN_EXCHANGE=false`.
- If Token Exchange cannot be disabled, restrict Public API access at the network level to trusted clients only.
- Disable unverified Community Package installation by setting `N8N_UNVERIFIED_PACKAGES_ENABLED=false` to eliminate the code execution path.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
JWTs issued through the Token Exchange module were assigned all Public API key scopes, regardless of the acting user's actual role. A low-privileged user who could obtain a valid external JWT trusted by a configured issuer could therefore use the resulting access token to invoke administrator-only Public API operations, such as role escalation, user creation, and user deletion.
The issue only affects instances where the Token Exchange feature and the Public API are enabled (N8N_TOKEN_EXCHANGE_ENABLED=true, N8N_ENV_FEAT_TOKEN_EXCHANGE=true) and the attacker can obtain an external JWT accepted by a configured trusted key. Role escalation additionally requires an Advanced Permissions license; Community Package installation additionally requires `N8N_COMMUNITY_PACKAGES_ENABLED=true` and `N8N_UNVERIFIED_PACKAGES_ENABLED=true`.
## Patches
The issue has been fixed in n8n version 2.30.1 and 2.29.8. Users should upgrade to this version or later to remediate the vulnerability.
## Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Disable the Token Exchange feature by setting `N8N_TOKEN_EXCHANGE_ENABLED=false` or `N8N_ENV_FEAT_TOKEN_EXCHANGE=false`.
- If Token Exchange cannot be disabled, restrict Public API access at the network level to trusted clients only.
- Disable unverified Community Package installation by setting `N8N_UNVERIFIED_PACKAGES_ENABLED=false` to eliminate the code execution path.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Vulnerability type
CWE-269
Improper Privilege Management
- https://github.com/n8n-io/n8n/security/advisories/GHSA-777w-rpr6-c52h vendor-advisory
- https://www.vulncheck.com/advisories/n8n-before-privilege-escalation-via-token-e... third-party-advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-65595
- https://github.com/n8n-io/n8n/releases/tag/[email protected]
- https://github.com/n8n-io/n8n/releases/tag/[email protected]
- https://github.com/advisories/GHSA-777w-rpr6-c52h
- https://github.com/n8n-io/n8n Product
Published: 22 Jul 2026 · Updated: 22 Jul 2026 · First seen: 22 Jul 2026