n8n-io n8n up to 1.123.26/2.13.2/2.14.0 Content-Security-Policy /rest/binary-data cross site scripting

Summaryinfo

A vulnerability was found in n8n-io n8n up to 1.123.26/2.13.2/2.14.0 and classified as problematic. This issue affects some unknown processing of the file /rest/binary-data of the component Content-Security-Policy Handler. Executing a manipulation can lead to cross site scripting. The identification of this vulnerability is CVE-2026-33749. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in n8n-io n8n up to 1.123.26/2.13.2/2.14.0 and classified as problematic. This vulnerability affects an unknown code of the file /rest/binary-data of the component Content-Security-Policy Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability was named CVE-2026-33749 since 03/23/2026. The exploitation appears to be easy. The attack can be initiated remotely. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.

Upgrading to version 1.123.27 or 2.13.3 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-15956). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• n8n-io

Name

• n8n

Version

• 1.123.0
• 1.123.1
• 1.123.2
• 1.123.3
• 1.123.4
• 1.123.5
• 1.123.6
• 1.123.7
• 1.123.8
• 1.123.9
• 1.123.10
• 1.123.11
• 1.123.12
• 1.123.13
• 1.123.14
• 1.123.15
• 1.123.16
• 1.123.17
• 1.123.18
• 1.123.19
• 1.123.20
• 1.123.21
• 1.123.22
• 1.123.23
• 1.123.24
• 1.123.25
• 1.123.26
• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.13.0
• 2.13.1
• 2.13.2
• 2.14.0

Website

• Product: https://github.com/n8n-io/n8n/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion