CVE-2026-27578: n8n · Basic XSS
Affects n8nSource CVE Database V5
Not known to be exploited · CVSS 8.5 High · fixed in 2.10.1 : patch n8n soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.10.1, 2.9.3, 1.123.22
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade n8n to 2.10.1, 2.9.3 or 1.123.22; n8n-io/n8n to 1.123.22.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
npmn8n-io/n8npkg:npm/n8n-io/n8nOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-27578, organizations should immediately upgrade n8n to versions 2.10.1, 2.9.3, or 1.123.22 or later where the vulnerability is patched. Until upgrades are feasible, restrict workflow creation and modification permissions strictly to fully trusted and vetted users to reduce the risk of malicious script injection. Additionally, disable the Webhook node by adding `n8n-nodes-base.webhook` to the `NODES_EXCLUDE` environment variable to limit attack vectors, though this is only a partial mitigation. Implement strict monitoring and auditing of workflow changes to detect suspicious activity. Employ Content Security Policy (CSP) headers to reduce the impact of injected scripts. Educate users to avoid clicking on suspicious links or workflows. Regularly review user permissions and remove unnecessary workflow editing rights. Finally, maintain up-to-date backups of workflows and configurations to enable recovery in case of compromise.
Description
n8n is an open source workflow automation platform. Prior to versions 2.10.1, 2.9.3, and 1.123.22, an authenticated user with permission to create or modify workflows could inject arbitrary scripts into pages rendered by the n8n application using different techniques on various nodes (Form Trigger node, Chat Trigger node, Send & Wait node, Webhook Node, and Chat Node). Scripts injected by a malicious workflow execute in the browser of any user who visits the affected page, enabling session hijacking and account takeover. The issues have been fixed in n8n versions 2.10.1 and 1.123.21. 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, and/or disable the Webhook node by adding `n8n-nodes-base.webhook` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
References
- github.com/n8n-io/n8n/security/advisories/GHSA-2p9h-rqjw-gm92 (opens in a new tab)
- github.com/n8n-io/n8n/commit/062644ef786b6af480afe4a0f12bc6d70040534a (opens in a new tab)
- github.com/n8n-io/n8n/commit/1479aab2d32fe0ee087f82b9038b1035c98be2f6 (opens in a new tab)
- github.com/n8n-io/n8n/commit/9e5212ecbc5d2d4e6f340b636a5e84be6369882e (opens in a new tab)