n8n: Stored XSS in Chat Trigger Node
Description
Impact
An authenticated user with workflow edit access could inject arbitrary JavaScript into the Chat Trigger's generated page by setting a malicious webhookId. When a logged-in user visited the chat URL, the injected code executed in the n8n origin with that user's session privileges.
Patches
The issue has been fixed in n8n versions 1.123.55, 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds
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 Chat Trigger node by adding @n8n/n8n-nodes-langchain.chatTrigger to the NODES_EXCLUDE environment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
n8nnpm | < 1.123.55 | 1.123.55 |
n8nnpm | >= 2.26.0, < 2.26.2 | 2.26.2 |
n8nnpm | >= 2.0.0-rc.0, < 2.25.7 | 2.25.7 |
Affected products
1Patches
Vulnerability mechanics
References
2News mentions
1- n8n: 16 CVEs Disclosed in Single Batch — Credential Leaks, Prototype Pollution, and Sandbox EscapeVypr Intelligence · Jun 16, 2026