CVE-2025-68613: n8n Improper Control of Dynamically-Managed Code Resources Vulnerability

Published Dec 19, 2025
·
Updated

Impact n8n contains a critical Remote Code Execution (RCE) vulnerability in its workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime.

An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations.

Patches This issue has been fixed in n8n v1.122.0.

Users are strongly advised to upgrade to version 1.122.0 or later, which introduces additional safeguards to restrict expression evaluation.

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 eliminate the risk and should only be used as short-term measures.

Other sources

n8n contains an improper control of dynamically managed code resources vulnerability in its workflow expression evaluation system that allows for remote code execution.

CISA

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or 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 eliminate the risk and should only be used as short-term measures.

NVD

Affected Software

6 affected componentsFixes available
npm/n8n>=0.211.0<1.120.4
npm/n8n>=1.121.0<1.121.1
1.121.1
npm/n8n>=0.211.0<1.120.4
1.120.4
n8n N8n Node.js>=0.211.0<1.120.4
n8n N8n Node.js=1.121.0
n8n n8n

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.121.1
  2. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.120.4
  3. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.122.0
  4. Configuration

    Limit workflow creation and editing permissions to fully trusted users only by configuring role/permission settings so only vetted administrators can create or modify workflows.

    n8n workflow_creation_and_editing_permissions = trusted_users_only
  5. Compensating control

    Deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation.

Event History

Dec 19, 2025
CVE Published
via MITRE·10:23 PM
Data Sourced
via MITRE·10:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Dec 22, 2025
Advisory Published
via GitHub·04:19 PM
Data Sourced
via GitHub·04:19 PM
DescriptionSeverityWeaknessAffected Software
Feb 4, 2026
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 11, 2026
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software
News Published
via BleepingComputer·06:21 PM
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-2025-68613?

CVE-2025-68613 is classified as a critical vulnerability due to its potential for remote code execution.

2

How do I fix CVE-2025-68613?

To fix CVE-2025-68613, upgrade n8n to version 1.120.4 or later.

3

Which versions of n8n are affected by CVE-2025-68613?

Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 are affected by CVE-2025-68613.

4

What type of vulnerability is CVE-2025-68613?

CVE-2025-68613 is a Remote Code Execution (RCE) vulnerability.

5

What can an attacker achieve with CVE-2025-68613?

An attacker exploiting CVE-2025-68613 can execute arbitrary code on the affected n8n instance.

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