n8n
Affected
- introduced
0, fixed1.123.55(semver)
Fixed versions
1.123.55
Fix
- Fixed version
1.123.55npm install [email protected]
Advisory
Also known as: CVE-2026-54301
n8n: Same-Origin XSS in Respond to Webhook Node
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:
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.
High Basis: The source's own band: HIGH
0, fixed 1.123.55 (semver)1.123.55
1.123.55npm install [email protected]2.26.0, fixed 2.26.2 (semver)2.26.2
2.26.2npm install [email protected]2.0.0-rc.0, fixed 2.25.7 (semver)2.25.7
2.25.7npm install [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0