EUVD-2026-47639
GHSA-wq64-hcrf-8m56
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid external JWT from trusted issuer
-
DeliveryExchange JWT via Token Exchange for access token
-
ExploitReceive token with all Public API scopes
-
ExecutionInvoke admin-only Public API (create/escalate user)
-
PersistInstall unverified Community Package
-
ImpactExecute arbitrary code on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an instance where BOTH the Token Exchange module and the Public API are enabled, and the attacker must be able to obtain a valid external JWT trusted by a configured issuer (this is the AT:P attack requirement and PR:L authentication level). Limiting factors: role-escalation specifically requires an Advanced Permissions license to be present; the remote-code-execution outcome additionally requires unverified Community Package installation to be enabled. Instances running default configurations without Token Exchange, without the Public API, or without a trust relationship to an attacker-obtainable issuer are not exploitable via this flaw. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H) scores 8.9, reflecting network reachability, low attacker privilege, and high confidentiality/integrity/availability impact, tempered by AT:P - a present attack requirement, namely possession of a valid external JWT trusted by a configured issuer. This is a genuine priority for instances that actually enable both Token Exchange and the Public API, but that dual-configuration prerequisite meaningfully narrows the exposed population; default n8n deployments without these features are not affected. There is no CISA KEV listing and no public exploit code identified, so exploitation is not confirmed in the wild. EPSS data was not provided in the input and cannot be cited. The most severe outcome (RCE) is further conditional on unverified Community Package installation being enabled, and role-escalation specifically requires an Advanced Permissions license - so the highest-impact chains depend on additional non-default settings. |
| Exploit ScenarioDerived | A low-privileged n8n user (or an attacker who has obtained a JWT from an external issuer the instance trusts) exchanges that JWT through the Token Exchange endpoint and receives an access token carrying all Public API scopes. Using that token they call admin-only Public API operations to create a new user, delete accounts, or - with an Advanced Permissions license present - escalate their own role; if unverified Community Package installation is enabled they install a malicious package to achieve remote code execution on the host. No public proof-of-concept has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 22, 2026
Privilege escalation and potential remote code execution affects n8n workflow-automation instances before 2.30.1 and 2.29.8 where both the Token Exchange module and Public API are enabled. Because JWTs issued via Token Exchange are granted the full set of Public API key scopes irrespective of the acting user's role, a low-privileged user holding a valid external JWT trusted by a configured issuer can invoke administrator-only operations - creating, deleting, or escalating users, and, where unverified Community Package installation is permitted, executing arbitrary code. No public exploit identified at time of analysis; VulnCheck-reported with a CVSS 4.0 base of 8.9.
RemediationAI
Upgrade to a fixed release: n8n 2.30.1 (current line) or 2.29.8 (maintenance line) per the vendor advisory GHSA-777w-rpr6-c52h. Where immediate upgrade is not possible, disable the Token Exchange module, which removes the vulnerable JWT issuance path entirely at the cost of any federated token-exchange login integrations; alternatively disable the Public API, which blocks the administrative endpoints the over-scoped token abuses but breaks any automation relying on the Public API. To specifically cut the RCE path, disable unverified Community Package installation so untrusted packages cannot be installed. As a network control, restrict access to the Public API and Token Exchange endpoints to trusted management networks. Confirm exact configuration flag names against the vendor advisory before applying, and validate that any external issuer trusted by Token Exchange is tightly scoped.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
n8n is a source-available workflow automation platform (fair-code) whose Public API exposes privileged administrative endpoints (user management, roles, etc.) gated by API-key scopes. The Token Exchange module lets an external, issuer-signed JWT be exchanged for an n8n access token, effectively federating identity from a trusted issuer. The root cause is CWE-269 (Improper Privilege Management): the scope-assignment logic for Token-Exchange-issued JWTs statically attaches every Public API scope rather than deriving scopes from the authenticated user's role, so the resulting access token over-privileges the bearer. The RCE path leverages n8n's Community Package installation feature - when it permits unverified/unsigned packages, a caller who can drive package installation can execute code within the n8n process.
Know when N8n gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Network-reachable and low-privileged (PR:L), but obtaining a trusted external JWT is an added requirement so AC:H; privilege escalation and RCE cross a trust boundary so S:C with full C/I/A impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
n8n before 2.30.1 and 2.29.8 assigns all Public API key scopes to JWTs issued through the Token Exchange module regardless of the acting user's role. On instances where the Token Exchange feature and Public API are enabled, a low-privileged user who can obtain a valid external JWT trusted by a configured issuer can use the resulting access token to invoke administrator-only Public API operations such as role escalation, user creation, and user deletion (role escalation requires an Advanced Permissions license), and, when unverified Community Package installation is enabled, achieve remote code execution.
Executive ViewAI
n8n workflow-automation instances with both Token Exchange and Public API modules enabled are vulnerable to privilege escalation and remote code execution when low-privileged users possess valid external JWTs. Attackers can assume administrator privileges, modify user accounts, and potentially execute arbitrary code on business-critical automation systems.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable Token Exchange module unless operationally required; (2) Restrict Public API JWT issuers to trusted identity providers only; (3) Disable unverified Community Package installation; (4) Implement monitoring and alerting for user creation, deletion, and privilege escalation operations; (5) Apply network segmentation to limit lateral movement if instance is compromised.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Remote code execution in n8n's workflow expression evaluation system allows an authenticated user with workflow creation
n8n workflow automation (through 1.121.2) allows authenticated users to execute arbitrary code via the n8n service, with
n8n workflow automation (1.65.0 to 1.121.0) allows unauthenticated file access through form-based workflows. A critical
n8n has a fifth critical RCE vulnerability (CVSS 9.9) in the Expression evaluator, enabling code execution through craft
Authenticated users who can create or modify an n8n workflow can achieve remote code execution on the n8n host by abusin
A prototype pollution vulnerability in the XML and GSuiteAdmin nodes of n8n workflow automation platform allows authenti
An authenticated user with workflow creation or modification privileges in n8n workflow automation platform can exploit
n8n-workflows Main Commit ee25413 allows attackers to execute a directory traversal via the download_workflow function w
Authenticated n8n users can hijack administrator accounts when LDAP authentication is enabled by manipulating their LDAP
The n8n package 0.218.0 for Node.js allows Escalation of Privileges. Rated high severity (CVSS 8.8), this vulnerability
SQL injection in n8n's Data Table Get node allows authenticated users with workflow modification permissions to execute
Authenticated users can exploit string formatting and exception handling in n8n's Python task executor to escape sandbox
Exploit-DB