# CVE-2026-25051: n8n XSS — Fixed in 1.123.2

📦 npm

Not in CISA KEV

# CVE-2026-25051 — n8n

[Fix: n8n-io/n8n@ced34c0](https://github.com/n8n-io/n8n/commit/ced34c0f93ab4c759a56065965986094d8ef7323)

CVE-2026-25051 is a Cross-site Scripting (XSS) vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

n8n Improper CSP Enforcement in Webhook Responses May Allow Stored XSS

Also known as[GHSA-825q-w924-xhgx](/vulnerability/GHSA-825q-w924-xhgx)

Published

Feb 4, 2026

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25051.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

0.00%0.25%0.50%0.76%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

36other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`n8n`npm

138Kdownloads / week

## Description

### 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

## Affected Packages

2 total 2 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`n8n` 

≥ 1.123.0&&< 1.123.2

1.123.2`npm install n8n@1.123.2`

📦npm

`n8n` 

all versions

1.122.5`npm install n8n@1.122.5`

## Affected Products

1 product · 1 configurations

Application

`n8n`n8n

< 1.123.2

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update n8n to 1.123.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25051 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
    

## Frequently Asked Questions

\## 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

O3 Security · Impact-Aware SCA

### Is CVE-2026-25051 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)