---
id: CVE-2026-54301
title: 'n8n: Same-Origin XSS in Respond to Webhook Node'
summary: 'n8n: Same-Origin XSS in Respond to Webhook Node'
severity: high
cvss: 7.6
cwe:
  - CWE-79
vendor: n8n
product: n8n
ecosystem: npm
affected:
  - n8n < 1.123.55
  - 'n8n >= 2.26.0, < 2.26.2'
  - 'n8n >= 2.0.0-rc.0, < 2.25.7'
patched:
  - n8n 1.123.55
  - n8n 2.26.2
  - n8n 2.25.7
published: '2026-06-16'
updated: '2026-06-16'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-v733-mwr6-fgcm'
references:
  - url: 'https://github.com/n8n-io/n8n/security/advisories/GHSA-v733-mwr6-fgcm'
  - url: 'https://github.com/advisories/GHSA-v733-mwr6-fgcm'
tags:
  - ghsa
  - npm
epss: 0.00238
epssPercentile: 0.1319
ingestedAt: '2026-06-29T14:31:47.722Z'
---

## Overview

## Impact
An authenticated user with workflow edit access could configure a `Respond to Webhook` node to serve binary content with an attacker-controlled `Content-Type`. The binary response path bypassed the central `Content-Security-Policy` sandbox header, allowing a public webhook to execute JavaScript in the n8n origin when visited by an authenticated user, with access to that user's session.

## 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 Respond to Webhook node by adding `n8n-nodes-base.respondToWebhook` to the `NODES_EXCLUDE` environment variable.

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

## Affected packages

- `n8n < 1.123.55`
- `n8n >= 2.26.0, < 2.26.2`
- `n8n >= 2.0.0-rc.0, < 2.25.7`

## Remediation

Upgrade to a patched release:

- `n8n 1.123.55`
- `n8n 2.26.2`
- `n8n 2.25.7`