CVE-2026-25049: n8n Has an Expression Escape Vulnerability Leading to RCE

Published Feb 4, 2026
·
Updated

Impact

Additional exploits in the expression evaluation of n8n have been identified and patched following CVE-2025-68613.

An authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n.

Patches

The issue has been fixed in n8n versions 1.123.17 and 2.5.2. Users should upgrade to these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

- Limit workflow creation and editing permissions to fully trusted users only. - Deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation.

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

Resources

- Best practices for securing n8n - Initial vulnerability advisory: CVE-2025-68613

---

n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backward compatibility.

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

Other sources

n8n is an open source workflow automation platform. Prior to versions 1.123.17 and 2.5.2, an authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n. This issue has been patched in versions 1.123.17 and 2.5.2.

MITRE

Affected Software

5 affected componentsFixes available
n8n/n8n<1.123.17, <2.5.2
npm/n8n>=2.0.0<2.5.2
2.5.2
npm/n8n<1.123.17
1.123.17
n8n N8n Node.js<1.123.17
n8n N8n Node.js>=2.0.0<2.5.2

Event History

Feb 4, 2026
CVE Published
via MITRE·04:46 PM
Data Sourced
via MITRE·04:46 PM
DescriptionWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:03 PM
Data Sourced
via GitHub·06:03 PM
DescriptionWeaknessAffected Software
News Published
via BleepingComputer·09:14 PM
News Published
via BleepingComputer·09:16 PM
Feb 5, 2026
News Published
via The Register·11:38 AM
News Published
via The Register·11:41 AM
Mar 12, 2026
News Published
via The Register·01:34 PM
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-25049?

CVE-2026-25049 has been identified as a critical vulnerability that can lead to remote code execution.

2

How do I fix CVE-2026-25049?

To mitigate CVE-2026-25049, upgrade to n8n versions 2.5.2 or 1.123.17.

3

Who is affected by CVE-2026-25049?

CVE-2026-25049 affects authenticated users of n8n versions below 1.123.17 and between 2.0.0 and 2.5.2.

4

What kind of vulnerability is CVE-2026-25049?

CVE-2026-25049 is an expression escape vulnerability that can be exploited for remote code execution.

5

Is there a patch available for CVE-2026-25049?

Yes, patches for CVE-2026-25049 are included in the updated n8n versions 2.5.2 and 1.123.17.

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