n8n Has Stored Cross-site Scripting via Markdown Rendering in Workflow UI
HighCVE-2026-25054 · Published Feb 4, 2026
## Impact A Cross-site Scripting (XSS) vulnerability existed in a markdown rendering component used in n8n's interface, including workflow sticky notes and other areas that support markdown content. An authenticated user with permission to create or modify workflows could abuse this to execute scripts with same-origin privileges when other users interact with a maliciously crafted workflow. This could lead to session hijacking and account takeover. ## Patches The issue has been fixed in n8n versions 2.2.1 and 1.123.9. Users should upgrade to 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. - Review existing workflows for potentially malicious markdown content in sticky notes and other components. - Educate users about the risks of opening workflows from untrusted sources. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. --- n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector st...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | >= 2.0.0, < 2.2.1 | 2.2.1 |
| < 1.123.9 | 1.123.9 |
Details and references
## Impact A Cross-site Scripting (XSS) vulnerability existed in a markdown rendering component used in n8n's interface, including workflow sticky notes and other areas that support markdown content. An authenticated user with permission to create or modify workflows could abuse this to execute scripts with same-origin privileges when other users interact with a maliciously crafted workflow. This could lead to session hijacking and account takeover. ## Patches The issue has been fixed in n8n versions 2.2.1 and 1.123.9. Users should upgrade to 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. - Review existing workflows for potentially malicious markdown content in sticky notes and other components. - Educate users about the risks of opening workflows from untrusted sources. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures. --- n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backward compatibility. CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
- CVSS 4.0
- CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-79
- Also known as
- CVE-2026-25054
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Feb 4 | n8n's domain allowlist bypass enables credential exfiltration MediumFeb 4 | Medium | 1.121.0 |
| Feb 4 | n8n has a Python sandbox escapeCritical9.9Feb 4 | Critical9.9 | 2.4.8 |
| Feb 4 | n8n Merge Node has Arbitrary File Write leading to RCECriticalFeb 4 | Critical | 1.118.0+1 more |
| Feb 4 | n8n Vulnerable to Arbitrary File Write on Remote Systems via SSH NodeHighFeb 4 | High | 1.123.12+1 more |
| Feb 4 | n8n has OS Command Injection in Git NodeCriticalFeb 4 | Critical | 1.123.10+1 more |
| Feb 4 | n8n's Improper File Access Controls Allow Arbitrary File Read by Authenticated UsersCriticalFeb 4 | Critical | 1.123.18+1 more |