CVE-2026-33749

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.

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-33749 has a CVSS score of 8.9 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.123.27, 2.14.1, 2.13.3); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-33749? CVE-2026-33749 is a medium-severity cross-site scripting (XSS) vulnerability in n8n (npm), affecting versions < 1.123.27. It is fixed in 1.123.27, 2.14.1, 2.13.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-33749? CVE-2026-33749 has a CVSS score of 8.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by CVE-2026-33749? n8n (npm) versions < 1.123.27 is affected.
4. Is there a fix for CVE-2026-33749? Yes. CVE-2026-33749 is fixed in 1.123.27, 2.14.1, 2.13.3. Upgrade to this version or later.
5. Is CVE-2026-33749 exploitable, and should I be worried? Whether CVE-2026-33749 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33749 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33749?
   • Upgrade n8n to 1.123.27 or later
   • Upgrade n8n to 2.14.1 or later
   • Upgrade n8n to 2.13.3 or later