n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox
CVE-2025-61914 · GHSA-58jc-rcg5-95f3 · published 2025-12-26 · updated 2025-12-27
- Severity
- High
- CVSS score
- 7.3
- Chance of exploitation (EPSS)
- 0.24%
- Fixed in
- 1.114.0
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
A stored Cross-Site Scripting (XSS) vulnerability may occur in n8n when using the “Respond to Webhook” node. When this node responds with HTML content containing executable scripts, the payload may execute directly in the top-level window, rather than within the expected sandbox introduced in version 1.103.0. This behavior can enable a malicious actor with workflow creation permissions to execute arbitrary JavaScript in the context of the n8n editor interface.
Upgrade n8n to 1.114.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The vulnerability has been patched in v.1.114.0.
Restrict workflow creation and modification privileges to trusted users only. Avoid using untrusted HTML responses in the “Respond to Webhook” node. Use an external reverse proxy or HTML sanitizer to filter responses that include executable scripts.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n | npm | < 1.114.0 | 1.114.0 |
- CriticalJupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSPjupyter-server
- CriticalMalicious website can execute commands on the local system through XSS in the OpenCode web UIopencode-ai
- CriticalFlowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panelflowise
- CriticalMLFlow Cross-site Scripting vulnerability leads to client-side Remote Code Executionmlflow
- CriticalCross-site Scripting in MLFlowmlflow
- HighPraisonAI: Prompt Injection Defense Bypassed for HIGH-Level Threatspraisonai
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.