Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as n8n member
-
DeliveryCreate and activate webhook workflow
-
ExploitReturn HTML via CSP-less response path
-
ExecutionLure victim to open webhook URL
-
ImpactScript runs on n8n origin with victim session
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 | Requires an authenticated n8n member with permission to create AND activate workflows (PR:L), plus a victim who opens the attacker's webhook URL (UI:A). The concrete trigger is a webhook response served through a path that omits n8n's sandbox Content-Security-Policy - specifically error responses and some responses without headers, including nodes operating in legacy response mode. Limiting factors: exploitation is not useful against a single-user/trusted instance (the dangerous case is shared or multi-tenant deployments where another, possibly higher-privileged, user opens the webhook URL); it needs the victim's interaction and a member-level account, so it is not remote-unauthenticated. The script executes on the n8n origin and acts with the session of whoever opens the URL. |
| Impact | This is a credible this-week-priority issue rather than an inflated high-CVSS score, but it is explicitly not a remote-unauthenticated catastrophe. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N) encodes exactly the gating factors that matter: network reach and low complexity, but privileges required (PR:L - the attacker must be an authenticated n8n member able to create and activate workflows) and active user interaction (UI:A - a victim must open the malicious webhook URL). The vulncheck Decision label is 'this_week', consistent with high confidentiality/integrity impact against the n8n origin via session riding. No CISA KEV listing is present in the input, no EPSS score was supplied, and no public exploit or PoC reference is provided (the two references are the GHSA and vulncheck advisories, not exploit code), so there is no evidence of active exploitation - treat the threat as plausible-but-unproven, driven by the stored/persistent nature of the XSS rather than mass exploitation. The main tension to flag: the impact ceiling depends on who opens the webhook URL (self-XSS-like unless a higher-privileged user is lured into opening an attacker-controlled webhook), so real-world severity hinges on multi-tenant/shared-instance deployments where a low-privilege member can reach other users' sessions. |
| Exploit ScenarioDerived | On a shared or multi-tenant n8n instance, a low-privileged but authenticated member creates and activates a workflow whose webhook returns HTML through a response path that omits the sandbox CSP - for example an error response or a legacy-mode response without headers. The member sends the webhook URL to another user; when that user opens it, the injected script executes on the n8n origin and acts with the victim's authenticated session. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Stored cross-site scripting in n8n allows an authenticated member who can create and activate workflows to serve attacker-supplied HTML from webhook response paths that skip n8n's sandbox Content-Security-Policy, so the markup executes on the n8n origin and can act with the session of any user who opens the webhook URL. The flaw affects releases before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1, and is fixed in 1.123.85, 2.43.5, and 2.44.1. Exploitation requires a member-level account plus a victim who opens the crafted webhook URL, making the practical risk highest in shared or multi-tenant instances rather than single-user or fully trusted deployments; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the issue is rated this_week priority.
RemediationAI
Vendor-released patch: upgrade to n8n 1.123.85, 2.43.5, or 2.44.1 (or later) per the GHSA advisory at https://github.com/n8n-io/n8n/security/advisories/GHSA-mp7q-23hg-35cf; note that 2.44.x users must move to 2.44.1 and 2.x users on earlier branches must move to 2.43.5 or later. The vendor states that upgrading is the remediation and that the following temporary mitigations do not fully remediate the risk: restrict access to the n8n instance to fully trusted users only (trade-off: limits collaboration and does not help multi-tenant deployments where the threat model is insider-to-insider), audit active webhook workflows and review response bodies returned by nodes operating in legacy response mode for unexpected HTML or script content (trade-off: detective only, requires re-review as workflows change), and apply network-level controls restricting /webhook/* routes to trusted sources (trade-off: breaks legitimate external webhook consumers and integrations if scoped too tightly).
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
n8n is a workflow automation platform in which users build workflows whose Webhook nodes return HTTP responses. To keep workflow-authored HTML from executing as a page on the n8n origin, n8n injects a sandbox Content-Security-Policy header into webhook responses. According to the vendor advisory, certain response paths - error responses and some responses without headers, including nodes operating in legacy response mode - were returned without that sandbox policy. This is a CWE-79 cross-site scripting issue rooted in missing output-side security policy enforcement rather than in input sanitization: the payload is delivered as a legitimate-looking webhook response body, and because the CSP header is absent the browser renders it in the context of the n8n origin. The consequence is that script served this way runs same-origin with n8n and inherits the session of the user who navigates to the webhook URL, allowing it to perform actions as that user. The trigger requires that a workflow author be able to create and activate a workflow that emits the malicious response through one of the uncovered paths; the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) marks the attacker as a low-privileged authenticated member and confirms the victim must interact by opening the URL, with scope change reflecting the pivot from the workflow author's privileges to the browsing user's session.
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:H/VA:N/SC:L/SI:L/SA:N
Authenticated member can create workflows (PR:L), victim must open the webhook URL (UI:R); script escapes the webhook sandbox to the n8n origin (S:C) with high C/I via session riding, no availability impact.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
2DescriptionCVE.org
n8n before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 contains a stored cross-site scripting vulnerability because some webhook response paths, such as error responses and responses without headers, omit the sandbox Content-Security-Policy. Authenticated members who can create and activate workflows can serve HTML that runs on the n8n origin, letting scripts act with the session of users who open the webhook URL.
Technical POC Analysis
CWE-79 (stored cross-site scripting) in n8n's webhook response handling.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
n8n workflow automation platform contains a stored cross-site scripting flaw that could allow a low-privileged user to execute malicious scripts in the context of other users' sessions. This poses a significant risk in multi-tenant or shared deployments where member-level accounts exist, potentially leading to session hijacking and unauthorized access to sensitive workflow data.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting member-level account creation and workflow activation rights, applying network-level access controls to limit exposure of webhook endpoints, and deploying a web application firewall to inspect and block malicious payloads.
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-112379
GHSA-j6xc-9gw8-942r
NVD
CVE.org
Exploit-DB