CVE-2026-65597
DOM XSS in n8n HTML preview allows same-origin script execution via iframe srcdoc
Is CVE-2026-65597 being exploited?
Not confirmed. CVE-2026-65597 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-65597?
CVE-2026-65597 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-65597?
Yes. A fix has been recorded for CVE-2026-65597. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65597 affect?
CVE-2026-65597 affects n8n before 1.123.64, n8n 2.x before 2.29.8, n8n before 2.30.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65597?
Upgrade to n8n 1.123.64, 2.29.8, or 2.30.1+ and limit global:member access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker (global:member) can execute scripts in a victim session, call APIs, steal tokens, modify or exfiltrate workflows/data.
Patch when possible
- affected< 1.123.64
- affected< 2.30.1
- affected< 2.29.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.