n8n Vulnerable to XSS via Binary Data Inline HTML Rendering

Summary

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.

Timeline

1. Mar 25, 2026, 6:39 PM UTCCVE published
2. Mar 25, 2026, 8:07 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Mar 25, 2026, 8:07 PM UTCRecord last updated

Affected versions

• n8n-io n8n

  fixed in 1.123.27; From 2.0.0-rc.0 · fixed in 2.13.3

• n8nnpm

  fixed in 1.123.27

• n8nnpm

  From 2.14.0 · fixed in 2.14.1

• n8nnpm

  From 2.0.0-rc.0 · fixed in 2.13.3

References 1