n8n
Affected
- introduced
0, fixed1.123.27(semver)
Fixed versions
1.123.27
Fix
- Fixed version
1.123.27npm install [email protected]
Advisory
Also known as: 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:
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Medium Basis: The source's own band: MODERATE
0, fixed 1.123.27 (semver)1.123.27
1.123.27npm install [email protected]2.14.0, fixed 2.14.1 (semver)2.14.1
2.14.1npm install [email protected]2.0.0-rc.0, fixed 2.13.3 (semver)2.13.3
2.13.3npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0