Advisoriesby Ibisn8n: Privilege Escalation and Code Execution via Full Public API Key Scope Assignment to Token Exchange JWTs
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=falseorN8N_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...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | >= 2.30.0, < 2.30.1 | 2.30.1 |
| < 2.29.8 | 2.29.8 |
Details and references
## 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.
- CVSS 4.0
- CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-269
- Also known as
- CVE-2026-65595
More n8n advisories
All n8n
n8n: Snowflake Node executeQuery Operation Allows SQL Injection via Unparameterized Expression InterpolationCVE-2026-72750fixed in 1.123.67 +2n8n: SQL injectionCVE-2026-72775fixed in 1.123.67 +2n8n: Cross-Tenant Module-Cache Poisoning in the JS Task RunnerCVE-2026-72764fixed in 1.123.67 +2n8n: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution DataCVE-2026-65589fixed in 1.123.64 +2n8n: Unauthenticated Endpoint Allows Cancellation of Any User's Active Test WebhookCVE-2026-65014fixed in 2.27.4n8n: GraphQL Node Bypasses "Allowed HTTP Request Domains" RestrictionCVE-2026-65596fixed in 1.123.64 +2