CVE-2026-25051: n8n Improper CSP Enforcement in Webhook Responses May Allow Stored XSS

Published Feb 4, 2026
·
Updated

Impact

A Cross-site Scripting (XSS) vulnerability has been identified in the handling of webhook responses and related HTTP endpoints. Under certain conditions, the Content Security Policy (CSP) sandbox protection intended to isolate HTML responses may not be applied correctly.

An authenticated user with permission to create or modify workflows could abuse this to execute malicious scripts with same-origin privileges when other users interact with the crafted workflow. This could lead to session hijacking and account takeover.

Patches

The issue has been fixed in n8n versions 1.122.5 and 1.123.2. Users should upgrade to 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. - Never execute untrusted workflows. - Review workflows that receive data from via webhooks, forms, or MCP servers to ensure they are communicating with trusted entities before executing them manually.

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

--- n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backward compatibility.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Other sources

n8n is an open source workflow automation platform. Prior to version 1.123.2, a Cross-Site Scripting (XSS) vulnerability has been identified in the handling of webhook responses and related HTTP endpoints. Under certain conditions, the Content Security Policy (CSP) sandbox protection intended to isolate HTML responses may not be applied correctly. An authenticated user with permission to create or modify workflows could abuse this to execute malicious scripts with same-origin privileges when other users interact with the crafted workflow. This could lead to session hijacking and account takeover. This issue has been patched in version 1.123.2.

MITRE

Affected Software

4 affected componentsFixes available
npm/n8n<1.123.2
npm/n8n<1.122.5
1.122.5
npm/n8n>=1.123.0<1.123.2
1.123.2
n8n N8n Node.js<1.123.2

Event History

Feb 4, 2026
CVE Published
via MITRE·04:46 PM
Data Sourced
via MITRE·04:46 PM
DescriptionWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:15 PM
Data Sourced
via GitHub·06:15 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-25051?

CVE-2026-25051 is categorized as a Cross-site Scripting (XSS) vulnerability with potential for high severity in certain configurations.

2

How do I fix CVE-2026-25051?

To resolve CVE-2026-25051, upgrade to n8n version 1.123.2 or above, or to 1.122.5 if you are using a prior version.

3

What software is affected by CVE-2026-25051?

CVE-2026-25051 affects n8n versions prior to 1.123.2 and includes specific versions between 1.123.0 and 1.123.2.

4

What are the potential impacts of CVE-2026-25051?

The potential impacts include the ability for attackers to execute arbitrary scripts in the context of users' browsers, leading to stored XSS.

5

Is there a workaround for CVE-2026-25051 if I cannot upgrade?

There are no documented workarounds for CVE-2026-25051, so upgrading is strongly recommended.

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