n8n-io n8n up to 1.123.21/2.9.2/2.10.0 Environment Variable NODES_EXCLUDE cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in n8n-io n8n up to 1.123.21/2.9.2/2.10.0. This issue affects some unknown processing of the component Environment Variable Handler. Such manipulation of the argument NODES_EXCLUDE leads to cross site scripting. This vulnerability is uniquely identified as CVE-2026-27578. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in n8n-io n8n up to 1.123.21/2.9.2/2.10.0. It has been rated as problematic. Affected by this issue is an unknown code block of the component Environment Variable Handler. The manipulation of the argument NODES_EXCLUDE with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. Impacted is integrity. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-27578 since 02/20/2026. The exploitation is known to be easy. The attack may be launched remotely. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.007.
Upgrading to version 1.123.22, 2.9.3 or 2.10.1 eliminates this vulnerability. Applying the patch 062644ef786b6af480afe4a0f12bc6d70040534a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0532). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Affected
- n8n n8n
Product
Vendor
Name
Version
- 1.123.0
- 1.123.1
- 1.123.2
- 1.123.3
- 1.123.4
- 1.123.5
- 1.123.6
- 1.123.7
- 1.123.8
- 1.123.9
- 1.123.10
- 1.123.11
- 1.123.12
- 1.123.13
- 1.123.14
- 1.123.15
- 1.123.16
- 1.123.17
- 1.123.18
- 1.123.19
- 1.123.20
- 1.123.21
- 2.0
- 2.1
- 2.2
- 2.3
- 2.4
- 2.5
- 2.6
- 2.7
- 2.8
- 2.9
- 2.9.0
- 2.9.1
- 2.9.2
- 2.10.0
License
Website
- Product: https://github.com/n8n-io/n8n/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: n8n 1.123.22/2.9.3/2.10.1
Patch: 062644ef786b6af480afe4a0f12bc6d70040534a
Timeline
02/20/2026 CVE reserved02/26/2026 Advisory disclosed
02/26/2026 VulDB entry created
03/04/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-2p9h-rqjw-gm92
Status: Confirmed
CVE: CVE-2026-27578 (🔒)
GCVE (CVE): GCVE-0-2026-27578
GCVE (VulDB): GCVE-100-347912
CERT Bund: WID-SEC-2026-0532 - n8n: Mehrere Schwachstellen
Entry
Created: 02/26/2026 01:35Updated: 03/04/2026 05:09
Changes: 02/26/2026 01:35 (71), 02/27/2026 08:17 (7), 03/01/2026 09:47 (1), 03/04/2026 05:09 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.