n8n: Same-Origin XSS in Respond to Webhook Node
- Product
- n8n
- CVE
- CVE-2026-54301
- Affected
- n8n before 1.123.55; n8n 2.0.0-rc.0 to 2.25.7; n8n 2.26.0 to 2.26.2
- Fixed in
- 1.123.55, 2.25.7, 2.26.2
Last verified against sources: October 26, 2026
Am I affected?
n8n: affected n8n before 1.123.55; n8n 2.0.0-rc.0 to 2.25.7; n8n 2.26.0 to 2.26.2. Fixed in 1.123.55, 2.25.7, 2.26.2.
- Check your version: run
npm ls n8n. Versions < 1.123.55 of n8n are affected. [1]
What to do now
- Upgrade to the fixed version: run
npm install n8n@1.123.55(first patched version 1.123.55). [1] - Upgrade to n8n 1.123.55, 2.25.7, or 2.26.2 or later to remediate the vulnerability. [1]
- Limit workflow creation and editing permissions to fully trusted users only. [1]
- Disable the Respond to Webhook node by adding n8n-nodes-base.respondToWebhook to the NODES_EXCLUDE environment variable. [1]
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
What happened
- An authenticated user with workflow edit access could configure a Respond to Webhook node to serve binary content with an attacker-controlled Content-Type. [1]
- The binary response path bypassed the central Content-Security-Policy sandbox header. [1]
- A public webhook could execute JavaScript in the n8n origin when visited by an authenticated user. [1]
Impact
- A public webhook could execute JavaScript in the n8n origin when visited by an authenticated user, with access to that user's session. [1]
What was done
Sources
- GHSA-v733-mwr6-fgcm — GitHub Advisory Database
Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.
Share advisory brief with your team
Copy a plain-text summary for Slack, GitHub issues, or team security channels.
[CVE-2026-54301] n8n: Same-Origin XSS in Respond to Webhook Node
Product: n8n | Affected: n8n before 1.123.55; n8n 2.0.0-rc.0 to 2.25.7; n8n 2.26.0 to 2.26.2 | Fixed in: 1.123.55, 2.25.7, 2.26.2
Summary: An authenticated user with workflow edit access could configure a Respond to Webhook node to serve binary content with an attacker-controlled Content-Type.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/06/cve-2026-54301-n8nCorrections
Report an error or request a correction. We review requests within 5 business days and add a dated correction note.
Discussions for CVE-2026-54301
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.