CVE-2026-65591
Authenticated workflow users can achieve host-level code execution via sanitizer bypass.
Is CVE-2026-65591 being exploited?
Not confirmed. CVE-2026-65591 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.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-65591?
CVE-2026-65591 is rated High. 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-65591?
Yes. A fix has been recorded for CVE-2026-65591. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-65591 affect?
CVE-2026-65591 affects n8n (legacy expression engine) — versions prior to 1.123.64, 2.29.8, 2.30.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65591?
Upgrade to 1.123.64, 2.29.8, or 2.30.1; restrict workflow create/modify permissions until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users with workflow create/modify can bypass the legacy expression sanitizer to execute arbitrary code as the n8n process (host-level RCE).
Immediate action required
- 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.