Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconAuthenticate as workflow author
-
DeliveryInject malicious script URL in Resource Locator dropdown
-
ExploitShare or export poisoned workflow
-
InstallVictim imports and opens node dropdown
-
C2Victim clicks external-link icon
-
ExecuteJavaScript executes in editor origin
-
ImpactSteal session tokens and workflow secrets
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution 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 authenticated n8n account with workflow-authoring privileges (PR:L) to craft and store a malicious script URL in a node's Resource Locator parameter dropdown. It is NOT remote-unauthenticated: a second, distinct user must actively interact (UI:A/UI:R) by opening the affected node's dropdown AND clicking the external-link icon for the payload to fire - passive viewing is insufficient. The vulnerability is in Resource Locator dropdown link handling specifically; impact is amplified in multi-user, collaborative, or workflow-sharing/import deployments because the payload persists across workflow imports and shares, enabling one poisoned workflow to target many victims over time. Single-user or isolated instances where authors only run their own workflows face minimal exposure. |
| Impact | This is a genuine but conditional, mid-tier priority issue rather than an urgent emergency. The vendor (VulnCheck) CVSS 4.0 score of 6.9 (AV:N/AC:L/AT:N/PR:L/UI:A) reflects two real limiters: the attacker must already be an authenticated workflow author (PR:L) and a second, different user must actively interact (UI:A) by opening the node dropdown and clicking the external-link icon. There is no EPSS score, no CISA KEV listing, and no public exploit code identified at time of analysis, so there is no evidence of active or automated exploitation - exploitation status is 'no public exploit identified at time of analysis.' The stored/persistent nature (payload survives workflow imports and shares) materially raises real risk versus a reflected XSS because a single malicious shared workflow can repeatedly target many collaborators who import it. The vendor rates confidentiality impact high (VC:H) since execution in the editor origin can access session material, API tokens, and workflow secrets of the victim; integrity and availability are limited (VI:L/VA:N). My own CVSS 3.1 assessment (~7.6, S:C/C:H/I:L) is directionally consistent but numerically higher than the 4.0 score because 3.1 weights the cross-user scope change and C:H more heavily than 4.0 weights UI:A+PR:L - a methodology discrepancy, not a disagreement on the facts. Net: patch on a normal cadence, prioritized for multi-tenant/shared-workflow n8n deployments where untrusted authors and marketplace/imported workflows are common. |
| Exploit ScenarioDerived | An attacker with a low-privilege workflow-author account on a shared n8n instance builds a workflow whose Resource Locator parameter dropdown contains a crafted malicious script URL, then shares or publishes it for import. When a higher-privileged colleague opens that node's dropdown and clicks the external-link icon, arbitrary JavaScript runs in the n8n editor origin, letting the attacker exfiltrate the victim's session/API credentials or act as them. No public proof-of-concept exploit is currently identified, but the persistence across imports and shares makes broad internal targeting straightforward once the poisoned workflow circulates. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Stored DOM cross-site scripting in the n8n workflow automation platform affects all releases before 1.123.80 on the 1.x line, 2.0.0 up to but not including 2.39.6, and 2.40.0 up to but not including 2.40.1. An authenticated user with workflow-authoring privileges can store a malicious script URL inside a node's Resource Locator parameter dropdown; when another user opens that node's dropdown and clicks the external-link icon, the injected JavaScript executes in the n8n editor origin. Because the payload is embedded in the workflow definition, it survives workflow imports and shares, allowing one poisoned workflow to reach multiple victims over time - though the assessed CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N) makes clear that a second, distinct user must actively click the link, so passive viewing is insufficient and single-user instances face minimal exposure. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied; the vendor has released patches, so this is a conditional mid-tier priority rather than an emergency.
RemediationAI
Vendor-released patch: upgrade to n8n 1.123.80 (1.x line), 2.39.6 (2.x stable line), or 2.40.1 (2.40.x line), as these are the fixed versions per the affected-version ranges in EUVD-2026-90643 and the vendor advisory. Patch availability is confirmed by both the vendor (GHSA-c2wp-6fgc-xjq4, https://github.com/n8n-io/n8n/security/advisories/GHSA-c2wp-6fgc-xjq4) and VulnCheck (https://www.vulncheck.com/advisories/n8n-before-1.123.80-2.39.6-and-2.40.1-stored-dom-xss-via-resource-locator); consult the advisory for the exact release notes for your track before upgrading. Until patching is complete, actionable compensating controls include: restricting workflow-authoring privileges to trusted users only, since exploitation requires author-level (PR:L) access to store the malicious Resource Locator URL - this reduces the attacker pool but does nothing against a trusted-but-malicious or compromised author; disabling or avoiding import/share of workflows from untrusted sources, and auditing existing workflow definitions for Resource Locator parameter values containing javascript:, data:, or other non-HTTP schemes - note this is a detective control that requires inspection of JSON and will not catch encoded or obfuscated payloads; and treating the issue as contained to the editor origin once triggered, so hardening browser CSP for the n8n editor reduces the blast radius but is not a substitute for the upgrade. The trade-off across all workarounds is that the authoritative fix is the version upgrade, and each interim control narrows either authoring convenience or workflow portability.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a CWE-79 improper neutralization of input during web page generation issue, specifically a stored DOM-based XSS in how n8n's editor renders Resource Locator parameter dropdowns. The Resource Locator parameter type is a core n8n editor UI construct that lets workflow authors pick resources (for example a file, channel, or ID) from connected services, and its dropdown surfaces an external-link affordance for URLs. The vulnerability arises because a URL value controlled by the workflow author is inserted into the dropdown's link handling without adequate sanitization of dangerous schemes such as javascript:, allowing script to execute in the context of the n8n editor origin (the scope-change, S:C, characteristic in the assessed vector). The DOM-based nature means the payload is parsed on the client as the dropdown is rendered, but the storage component - the malicious URL living inside the workflow's node parameters - is what elevates this from reflected to stored: it is persisted in the workflow JSON and therefore re-delivered on every import, share, or copy of that workflow. The CPE cpe:2.3:a:n8n-io:n8n confirms the affected component is the upstream n8n-io:n8n package, matching the vendor advisory GHSA-c2wp-6fgc-xjq4 and the VulnCheck advisory. The NVD-assigned CVSS 4.0 score of 6.9 (AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N) is consistent with the independent CVSS:3.1 assessment: both require an authenticated author (PR:L) and an additional user action (UI:A/UI:R), and both reflect high confidentiality impact against the editor session with only limited integrity impact.
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:N/PR:L/UI:A/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N
Authed author needed (PR:L) and victim must click the external-link icon (UI:R); cross-user execution in editor origin is a scope change (S:C) enabling session/secret theft (C:H).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a stored DOM cross-site scripting vulnerability in Resource Locator parameter dropdown link handling. Workflow authors can inject malicious script URLs that execute arbitrary JavaScript in the editor origin when other users open the node dropdown and click the external-link icon, with the payload persisting across workflow imports and shares.
Threat Intelligence Overview
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
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
EUVD-2026-90643
GHSA-7g6m-6jgv-fqm4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB