CVE-2026-103249: n8n: stored DOM XSS in Resource Locator dropdown
HIGHn8n, a widely used workflow automation and AI agent orchestration platform, has a stored DOM XSS flaw in its Resource Locator dropdown: a workflow author can plant a malicious script URL that runs JavaScript in the editor origin when another user clicks the external-link icon, and the payload persists across workflow imports and shares. The CVSS of 7.6 is driven by the changed scope and high confidentiality impact, because script running in the editor origin can reach session data and the credentials and API keys that n8n workflows commonly hold for LLM providers, databases and SaaS tools. Likelihood of exploitation is modest: EPSS is 0.00212 (89th percentile), the CVE is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK. The package has 244 other CVEs on record, which points to a heavily scrutinized attack surface, and the OpenSSF Scorecard of 6.7/10 is only middling. Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later, and until then review imported or shared workflows from untrusted authors for javascript: URLs in Resource Locator parameters.
What is the risk?
Medium-high. The attack is network-reachable with low complexity, but it needs an authenticated workflow author (PR:L) and a victim who opens the node dropdown and clicks the external-link icon (UI:R). The changed scope and high confidentiality impact make it serious in multi-user instances where lower-privileged authors can share workflows with admins or other users. Observed exploitation signals are weak (not in KEV, no public exploit, low EPSS), so the near-term risk is mainly insider or compromised-account abuse, or malicious workflow templates shared from untrusted sources. The patch ranges in the advisory are version-based, so unpatched self-hosted instances remain exposed until they are upgraded.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| n8n | npm | — | No patch |
Do you use n8n? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade n8n to 1.123.80 or later on the 1.x line, 2.39.6 or later on 2.0.x-2.39.x, or 2.40.1 or later on 2.40.x. 2) Until patched, restrict workflow creation and sharing rights to trusted users and avoid importing workflows or templates from unvetted sources. 3) Audit existing workflows, especially imported or shared ones, for Resource Locator parameters containing javascript: or other non-http(s) URLs. 4) Enforce a strict Content Security Policy on the n8n editor to limit inline script execution, and keep the editor behind SSO and network access controls. 5) Rotate credentials stored in n8n if you suspect a malicious workflow was opened by a privileged user, and review audit logs for unexpected credential or workflow changes. 6) Subscribe to the n8n GitHub advisory (GHSA-c2wp-6fgc-xjq4) for updates.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-103249?
n8n, a widely used workflow automation and AI agent orchestration platform, has a stored DOM XSS flaw in its Resource Locator dropdown: a workflow author can plant a malicious script URL that runs JavaScript in the editor origin when another user clicks the external-link icon, and the payload persists across workflow imports and shares. The CVSS of 7.6 is driven by the changed scope and high confidentiality impact, because script running in the editor origin can reach session data and the credentials and API keys that n8n workflows commonly hold for LLM providers, databases and SaaS tools. Likelihood of exploitation is modest: EPSS is 0.00212 (89th percentile), the CVE is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK. The package has 244 other CVEs on record, which points to a heavily scrutinized attack surface, and the OpenSSF Scorecard of 6.7/10 is only middling. Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later, and until then review imported or shared workflows from untrusted authors for javascript: URLs in Resource Locator parameters.
Is CVE-2026-103249 actively exploited?
No confirmed active exploitation of CVE-2026-103249 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-103249?
1) Upgrade n8n to 1.123.80 or later on the 1.x line, 2.39.6 or later on 2.0.x-2.39.x, or 2.40.1 or later on 2.40.x. 2) Until patched, restrict workflow creation and sharing rights to trusted users and avoid importing workflows or templates from unvetted sources. 3) Audit existing workflows, especially imported or shared ones, for Resource Locator parameters containing javascript: or other non-http(s) URLs. 4) Enforce a strict Content Security Policy on the n8n editor to limit inline script execution, and keep the editor behind SSO and network access controls. 5) Rotate credentials stored in n8n if you suspect a malicious workflow was opened by a privileged user, and review audit logs for unexpected credential or workflow changes. 6) Subscribe to the n8n GitHub advisory (GHSA-c2wp-6fgc-xjq4) for updates.
What systems are affected by CVE-2026-103249?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, workflow automation platforms, LLM orchestration pipelines, multi-user low-code AI platforms.
What is the CVSS score for CVE-2026-103249?
CVE-2026-103249 has a CVSS v3.1 base score of 7.6 (HIGH). The EPSS exploitation probability is 0.21%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0011.003Malicious LinkAML.T0049Exploit Public-Facing ApplicationAML.T0083Credentials from AI Agent ConfigurationCompliance Controls Affected
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An attacker with a low-privilege author account, or a malicious community template, creates a workflow whose Resource Locator parameter carries a javascript: URL. The workflow is shared with or imported by an administrator who runs AI agent automations. When the administrator opens the node dropdown and clicks the external-link icon, the script runs in the n8n editor origin, steals the session or calls the internal API, and extracts stored credentials such as LLM provider keys and database connections. Because the payload persists in the workflow, it keeps firing for every user who later opens that node.
Weaknesses (CWE)
CWE-79Improper Neutralization of Input During Web Page GenerationPrimaryCWE-79Improper Neutralization of Input During Web Page GenerationCWE-79 — Improper Neutralization of Input During Web Page Generation: The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
- [Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
- [Implementation, Architecture and Design] Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies. For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters. Parts of the same output document may require different encodings, which will vary depending on whether the output is in the: etc. Note that HTML Entity Encoding is only appropriate for the HTML body. Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed. HTML body Element attributes (such as src="XYZ") URIs JavaScript sections Casca
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:NReferences
Timeline
Related Vulnerabilities
CVE-2026-3366310.0n8n: member role steals plaintext HTTP credentials
Same package: n8nCVE-2026-3366010.0TensorFlow: type confusion NPD in tensor conversion
Same package: n8nCVE-2026-2185810.0n8n: Input Validation flaw enables exploitation
Same package: n8nCVE-2026-275779.9n8n: Code Injection enables RCE
Same package: n8nCVE-2026-274949.9n8n: security flaw enables exploitation
Same package: n8n