CVE-2026-65591: n8n code execution via sanitizer bypass in legacy expression evaluator

CVE-2026-65591 · Severity: high · CVSS 4 · Published 2026-07-22

n8n is a popular workflow automation tool used to connect various business applications and services. A security flaw in its legacy expression engine allows an authorized user to bypass safety filters and execute unauthorized commands on the underlying server. This could lead to a complete takeover of the n8n instance, potentially exposing sensitive credentials and automated business data.

Technologies: N8n, n8n (npm). Vendors: N8n, npm.

Quick answers

Is CVE-2026-65591 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-65591 being exploited in the wild.
How severe is CVE-2026-65591?
High severity, with a CVSS score of 4, published 22 July 2026.
Which products and versions are affected?
N8n < 1.123.64, < 2.29.8, < 2.30.1, < 1.123.64, >= 2.0.0-rc.0 < 2.29.8, >= 2.30.0 < 2.30.1; n8n (npm) SEMVER:introduced=0,fixed=1.123.64.
Is there a fix for CVE-2026-65591?
Yes. n8n (npm): upgrade to 1.123.64 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-65591 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-65591?
Check whether you run N8n or n8n (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • n8n (npm): upgrade to 1.123.64 or later
    npm install n8n@1.123.64

Technical details

A vulnerability exists in n8n's legacy expression evaluator where the computed-member sanitizer can be bypassed. This is classified as an Expression Language Injection (CWE-917). An authenticated attacker with permissions to create or modify workflows can craft a malicious expression that escapes the sandbox, leading to host-level code execution as the n8n process. The legacy engine is the default in affected versions. The issue is resolved in versions 1.123.64, 2.29.8, and 2.30.1. A temporary workaround involves switching the expression engine to 'vm' via environment variables.

Affected products

  • n8n-io n8n < 1.123.64, >= 2.0.0-rc.0 < 2.29.8, >= 2.30.0 < 2.30.1

Identifiers

  • CVE-2026-65591
  • GHSA-pm35-fqvh-cq5g

Timeline

  • 2026-07-08: disclosed: Initial report by Junming Wu (Dremig)
  • 2026-07-22: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.