CVE-2026-65591: n8n before 1.123.64 Sanitizer Bypass Remote Code Execution

Published Jul 22, 2026
·
Updated

Impact The legacy expression evaluator's computed-member sanitizer can be bypassed by an authenticated user with workflow create or modify permissions. Successful exploitation grants the attacker host-level code execution as the n8n process.

The legacy expression engine is the default engine in affected versions.

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. - Switch to the non-legacy expression engine by setting N8NEXPRESSIONENGINE=vm.

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

Other sources

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.

MITRE

Affected Software

10 affected componentsFixes available
n8n<1.123.64, >1.123.64<2.29.8, >2.29.8<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

    Switch to the non-legacy expression engine by setting N8N_EXPRESSION_ENGINE=vm (temporary mitigation if immediate upgrade is not possible).

    n8n N8N_EXPRESSION_ENGINE = vm
  8. Compensating control

    Restrict access to the n8n instance to fully trusted users only (temporary mitigation if immediate upgrade is not possible).

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·10:02 PM
Data Sourced
via GitHub·10:02 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-65591?

CVE-2026-65591 has been rated with a severity score of high at 8.9 according to the CVSS.

2

How does CVE-2026-65591 affect n8n?

CVE-2026-65591 allows an authenticated user with workflow permissions to bypass the sanitizer, leading to remote code execution on the host.

3

What are the potential risks of CVE-2026-65591?

The exploitation of CVE-2026-65591 can lead to host-level code execution, compromising the integrity and security of the affected n8n instance.

4

How can I fix CVE-2026-65591?

To fix CVE-2026-65591, users should update to n8n version 1.123.64 or later, which includes mitigations for this vulnerability.

5

Who is affected by CVE-2026-65591?

Any authenticated user with permissions to create or modify workflows in n8n versions before 1.123.64 is at risk from CVE-2026-65591.

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