CVE-2026-54302: n8n: Stored XSS in Chat Trigger Node

Published Jun 16, 2026
·
Updated

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 NODESEXCLUDE environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Other sources

n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, 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. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.

MITRE

Affected Software

6 affected componentsFixes available
npm/n8n>=2.0.0-rc.0<2.25.7
2.25.7
npm/n8n>=2.26.0<2.26.2
2.26.2
npm/n8n<1.123.55
1.123.55
n8n N8n Node.js<1.123.55
n8n N8n Node.js>=2.0.0<2.25.7
n8n N8n Node.js>=2.26.0<2.26.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.25.7
  2. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.26.2
  3. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.123.55
  4. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 1.123.55
  5. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.25.7
  6. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.26.2
  7. Configuration

    Temporarily mitigate by disabling the Chat Trigger node: add `@n8n/n8n-nodes-langchain.chatTrigger` to the `NODES_EXCLUDE` environment variable.

    n8n NODES_EXCLUDE = @n8n/n8n-nodes-langchain.chatTrigger
  8. Compensating control

    Temporarily mitigate by limiting workflow creation and editing permissions to fully trusted users only (authenticated users with workflow edit access could set a malicious `webhookId` to inject JavaScript).

Event History

Jun 16, 2026
Advisory Published
via GitHub·10:39 PM
Data Sourced
via GitHub·10:39 PM
DescriptionSeverityWeaknessAffected Software
Jun 23, 2026
CVE Published
via MITRE·03:46 PM
Data Sourced
via MITRE·03:46 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-54302?

CVE-2026-54302 has a severity rating of high with a score of 7.6.

2

How do I fix CVE-2026-54302?

To fix CVE-2026-54302, update n8n to the latest version where the vulnerability is patched.

3

What kind of vulnerability is CVE-2026-54302?

CVE-2026-54302 is a Cross-Site Scripting (XSS) vulnerability.

4

Who is affected by CVE-2026-54302?

Authenticated users with workflow edit access in n8n are affected by CVE-2026-54302.

5

What is the risk of CVE-2026-54302 exploitation?

The risk of exploiting CVE-2026-54302 is high, as it allows attackers to inject arbitrary JavaScript into user sessions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203