CVE-2026-65597: n8n before 1.123.64 DOM-Based XSS via Unsandboxed iframe

Published Jul 22, 2026
·
Updated

Impact

The HTML preview renders execution output into an iframe srcdoc without sandbox, so a sanitizer bypass lets injected script run same-origin as the editor. When a victim opens the preview, it can call authenticated APIs with their session. An account with global:member privileges can exploit it.

Patches

The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.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: - Restrict n8n instance access to fully trusted users only. - Set the N8NCONTENTSECURITYPOLICY environment variable to a policy that blocks inline scripts. - Avoid exposing workflows that render externally-controlled input into the HTML node or binary HTML preview to untrusted users.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Other sources

n8n before 1.123.64, 2.x before 2.29.8, and before 2.30.1 contains a DOM-based cross-site scripting vulnerability in the HTML preview, which renders execution output into an iframe srcdoc without the sandbox attribute. A sanitizer bypass allows injected script to execute same-origin as the editor. When a victim opens the preview, the script can call authenticated APIs using the victim's session. An account with global:member privileges can exploit the issue.

MITRE

Affected Software

12 affected componentsFixes available
n8n n8n<1.123.64
n8n n8n<2.29.8
n8n n8n<2.30.1
npm/n8n>=2.0.0-rc.0<2.29.8
2.29.8
npm/n8n>=2.30.0<2.30.1
2.30.1
npm/n8n<1.123.64
1.123.64
n8n N8n Node.js<1.123.64
n8n N8n Node.js<1.123.64
n8n N8n Node.js>=2.0.0<2.29.8
n8n N8n Node.js>=2.0.0<2.29.8
n8n N8n Node.js=2.30.0
n8n N8n Node.js=2.30.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.29.8
  2. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.30.1
  3. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.123.64
  4. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 1.123.64
  5. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.29.8
  6. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.30.1
  7. Configuration

    Set the N8N_CONTENT_SECURITY_POLICY environment variable to a Content Security Policy that blocks inline scripts to mitigate DOM-based XSS via the HTML preview.

    n8n N8N_CONTENT_SECURITY_POLICY = a policy that blocks inline scripts
  8. Compensating control

    Restrict n8n instance access to fully trusted users only, since an account with global:member privileges can exploit the issue.

  9. Compensating control

    Avoid exposing workflows that render externally-controlled input into the HTML node or binary HTML preview to untrusted users.

Event History

Jul 22, 2026
CVE Published
via MITRE·11:21 AM
Data Sourced
via MITRE·11:21 AM
DescriptionWeakness
Data Sourced
via NVD·12:18 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:18 PM
Affected Software
Advisory Published
via GitHub·05:57 PM
Data Sourced
via GitHub·05:57 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-65597?

CVE-2026-65597 has a severity rating of high, with a CVSS score of 8.2.

2

How do I fix CVE-2026-65597?

To fix CVE-2026-65597, upgrade n8n to version 1.123.64 or higher, where this vulnerability has been addressed.

3

What does CVE-2026-65597 exploit?

CVE-2026-65597 exploits a DOM-Based XSS vulnerability by using an unsandboxed iframe in n8n.

4

What are the potential impacts of CVE-2026-65597?

The potential impacts include unauthorized execution of scripts that can call authenticated APIs with the user's session.

5

Who is affected by CVE-2026-65597?

Users with n8n versions before 1.123.64, particularly those with global:member privileges, are affected by CVE-2026-65597.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203