CVE-2026-33749: n8n Vulnerable to XSS via Binary Data Inline HTML Rendering

Published Mar 25, 2026
·
Updated

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

7 affected componentsFixes available
n8n n8n<1.123.27, <2.13.3, <2.14.1
npm/n8n>=2.0.0-rc.0<2.13.3
2.13.3
npm/n8n=2.14.0
2.14.1
npm/n8n<1.123.27
1.123.27
n8n N8n Node.js<1.123.27
n8n N8n Node.js>=2.0.0<2.13.3
n8n N8n Node.js=2.14.0

Event History

Mar 25, 2026
CVE Published
via MITRE·06:39 PM
Data Sourced
via MITRE·06:39 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected Software
Mar 26, 2026
Advisory Published
via GitHub·06:28 PM
Data Sourced
via GitHub·06:28 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-33749?

CVE-2026-33749 has been classified as a medium severity vulnerability.

2

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.

3

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.

4

What type of vulnerability is CVE-2026-33749?

CVE-2026-33749 is an XSS vulnerability related to binary data inline HTML rendering in n8n.

5

Can CVE-2026-33749 be exploited remotely?

CVE-2026-33749 requires authentication, so it cannot be exploited remotely without valid user credentials.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203