CVE-2026-33749: n8n Vulnerable to XSS via Binary Data Inline HTML Rendering
Impact An authenticated user with permission to create or modify workflows could craft a workflow that produces an HTML binary data object without a filename. The /rest/binary-data endpoint served such responses inline on the n8n origin without Content-Disposition or Content-Security-Policy headers, allowing the HTML to render in the browser with full same-origin JavaScript access.
By sending the resulting URL to a higher-privileged user, an attacker could execute JavaScript in the victim's authenticated session, enabling exfiltration of workflows and credentials, modification of workflows, or privilege escalation to admin.
Patches The issue has been fixed in n8n versions 1.123.27, 2.13.3, and 2.14.1. 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. - Restrict network access to the n8n instance to prevent untrusted users from accessing binary data URLs.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
n8n is an open source workflow automation platform. Prior to versions 1.123.27, 2.13.3, and 2.14.1, an authenticated user with permission to create or modify workflows could craft a workflow that produces an HTML binary data object without a filename. The /rest/binary-data endpoint served such responses inline on the n8n origin without Content-Disposition or Content-Security-Policy headers, allowing the HTML to render in the browser with full same-origin JavaScript access. By sending the resulting URL to a higher-privileged user, an attacker could execute JavaScript in the victim's authenticated session, enabling exfiltration of workflows and credentials, modification of workflows, or privilege escalation to admin. The issue has been fixed in n8n versions 1.123.27, 2.13.3, and 2.14.1. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, and/or restrict network access to the n8n instance to prevent untrusted users from accessing binary data URLs. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33749?
CVE-2026-33749 has been classified as a medium severity vulnerability.
How do I fix CVE-2026-33749?
To fix CVE-2026-33749, upgrade n8n to versions 1.123.27, 2.13.3, or 2.14.1 or later.
Who is affected by CVE-2026-33749?
CVE-2026-33749 affects authenticated users of n8n prior to the specified versions that can create or modify workflows.
What type of vulnerability is CVE-2026-33749?
CVE-2026-33749 is an XSS vulnerability related to binary data inline HTML rendering in n8n.
Can CVE-2026-33749 be exploited remotely?
CVE-2026-33749 requires authentication, so it cannot be exploited remotely without valid user credentials.