CVE-2026-54301

Description

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

How to fix CVE-2026-54301

To remediate CVE-2026-54301, upgrade the affected package to a fixed version below.

• —upgrade to 1.123.55 or later

Is CVE-2026-54301 being exploited?

No exploitation signal available. Neither CISA KEV nor a current EPSS score has been published for CVE-2026-54301.

Affected packages (1)

• from 0, < 1.123.55

CVSS scores

References (2)

• PATCHgithub.com/n8n-io/n8n
• WEBgithub.com/n8n-io/n8n/security/advisories/GHSA-v733-mwr6-fgcm