Which versions of n8n are affected by CVE-2026-65591?

A host-level remote code execution vulnerability in n8n (CVE-2026-65591) allows authenticated workflow creators to execute arbitrary code as the n8n process through malicious expressions.. A patch is available.

How to fix or mitigate CVE-2026-65591?

Within 24 hours: Immediately restrict workflow create and modify permissions to essential personnel only and audit current role assignments to disable unnecessary access. Within 7 days: Implement mandatory approval workflows for new and modified workflows; enable comprehensive audit logging for all workflow changes; and monitor active workflows for suspicious expression patterns. Within 30 days: Evaluate whether the legacy expression engine can be disabled in favor of newer alternatives; engage with n8n for patch timeline and security guidance; and establish an upgrade plan with target completion date.

n8n CVE-2026-65591

Q: What is the CVSS score of CVE-2026-65591?

CVE-2026-65591 has a CVSS 4.0 base score of 8.9 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.5%.

EUVD-2026-47635 HIGH

Improper Neutralization of Special Elements used in an Expression Language Statement (CWE-917)

2026-07-22 VulnCheck

GHSA-m7jc-p4hf-xhwq

GHSA-pm35-fqvh-cq5g

RCE N8n

8.9

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

8.9 HIGH

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.5 HIGH

Authenticated workflow-editor (PR:L) exploits a sanitizer bypass with an extra attack requirement (AC:H) over the network to run host code; scope changes (S:C) as the process is fully compromised.

3.1 AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 22, 2026 - 13:02 EUVD

Analysis Generated

Jul 22, 2026 - 12:24 vuln.today

CVE Published

Jul 22, 2026 - 11:21 cve.org

HIGH 8.9

DescriptionCVE.org

n8n contains a sanitizer bypass vulnerability in the legacy expression evaluator's computed-member handler. An authenticated user with workflow create or modify permissions can craft a malicious expression to bypass the sanitizer and achieve host-level code execution as the n8n process. The legacy expression engine is the default in affected versions. Fixed in n8n 1.123.64, 2.29.8, and 2.30.1.

AnalysisAI

Host-level remote code execution in n8n (n8n-io) occurs when an authenticated user with workflow create or modify permissions crafts a malicious expression that bypasses the sanitizer in the legacy expression evaluator's computed-member handler, executing arbitrary code as the n8n process. Because the legacy expression engine is the default in affected versions, standard deployments are exposed without any special configuration. No public exploit identified at time of analysis, though the flaw was reported by VulnCheck and carries a high CVSS 4.0 base score of 8.9.

Technical ContextAI

n8n is a source-available workflow-automation platform where nodes and parameters can contain expressions evaluated at runtime. This issue lives in the legacy expression evaluator - the default engine in affected releases - specifically in the handler that resolves computed-member access (bracket/property lookups). The root cause maps to CWE-917 (Expression Language Injection / improper neutralization of special elements used in an expression language statement): the sanitizer intended to restrict what expressions can reference is bypassable through crafted computed-member access, allowing an attacker to reach and invoke host primitives and break out into arbitrary code execution in the Node.js process running n8n. CPE data confirms the affected product as cpe:2.3:a:n8n-io:n8n across an open version range up to the fixed builds.

RemediationAI

Upgrade to a patched build appropriate to your branch: n8n 1.123.64, 2.29.8, or 2.30.1 (Vendor-released patch per advisory GHSA-pm35-fqvh-cq5g). Until you can patch, reduce exposure by tightly restricting which users hold workflow create or modify permissions, since exploitation requires that privilege - audit RBAC assignments and remove editing rights from accounts that do not need them. Additionally, avoid exposing the n8n editor/API to untrusted networks by placing it behind a VPN or authenticated reverse proxy and network-segmenting the host, and run the n8n process under a least-privileged, sandboxed/containerized service account so that a successful RCE is contained rather than granting broad host access; the trade-off is added operational overhead and, for restrictive RBAC, reduced self-service workflow authoring for end users. Reference the vendor advisory (https://github.com/n8n-io/n8n/security/advisories/GHSA-pm35-fqvh-cq5g) and VulnCheck advisory (https://www.vulncheck.com/advisories/n8n-before-sanitizer-bypass-remote-code-execution) for authoritative fix details.