n8n has a Stored XSS Vulnerability in its Form Trigger
CVE-2026-56358 · GHSA-q4fm-pjq6-m63g · published 2026-03-27 · updated 2026-07-20
- Severity
- Medium
- CVSS score
- 5.4
- Chance of exploitation (EPSS)
- 0.24%
- Fixed in
- 2.11.2
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
An authenticated user with permission to create or modify workflows could exploit a flaw in the Form Trigger node's CSS sanitization to store a cross-site scripting (XSS) payload. The injected script executes persistently for every visitor of the published form, enabling form submission hijacking and phishing. The existing Content Security Policy prevents direct n8n session cookie theft but does not prevent script execution or form action manipulation.
Upgrade n8n to 2.11.2 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 issue has been fixed in n8n versions 2.12.0, 2.11.2, and 1.123.25. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only. Disable the Form Trigger node by adding n8n-nodes-base.formTrigger to the NODES_EXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- 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.