Advisory

GHSA-v733-mwr6-fgcm

Also known as: CVE-2026-54301

Summary

n8n: Same-Origin XSS in Respond to Webhook Node

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-06-16 19:00 UTC
Modified
2026-07-20 14:00 UTC

Affected packages and fixes

n8n

npm · All systems

Affected

  • introduced 0, fixed 1.123.55 (semver)

Fixed versions

1.123.55

Fix

n8n

npm · All systems

Affected

  • introduced 2.26.0, fixed 2.26.2 (semver)

Fixed versions

2.26.2

Fix

n8n

npm · All systems

Affected

  • introduced 2.0.0-rc.0, fixed 2.25.7 (semver)

Fixed versions

2.25.7

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences