Skip to content
Server Security Center
KEVcritical10.0

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

n8n · listed in the CISA catalog of actively exploited vulnerabilities since 2026-03-11.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
98%
among the highest 0.1% of all CVEs
Added to CISA KEV
2026-03-11
US federal due date 2026-03-25
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-68613 explained

CVE-2025-68613 is a critical remote code execution flaw in the workflow expression evaluation system of n8n, an open source workflow automation platform. Expressions supplied by authenticated users during workflow configuration may run in a context that is not sufficiently isolated from the underlying runtime. CISA lists it as known exploited, and a successful attack can fully compromise the instance.

Impact

An authenticated attacker with low privileges can execute arbitrary code over the network with the privileges of the n8n process. No user interaction is needed. This can lead to full compromise of the instance, including access to sensitive data, changes to workflows and system-level operations. CISA rates the technical impact as total but not automatable. Attackers are known to exploit it.

Who is affected

The CVE record lists affected n8n-io n8n versions as ≥ 0.211.0, < 1.120.4 and 1.121.0. The description says versions starting with 0.211.0 and prior to 1.120.4, 1.121.1 and 1.122.0 are affected. The record's structured version data names no fixed version, but the description states the issue is fixed in 1.120.4, 1.121.1 and 1.122.0.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • n8n-io n8n
    Affected
    • ≥ 0.211.0
    • < 1.120.4
    • 1.121.0
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: github.com/n8n-io/n8n/security/advisories/GHSA-v98v-ff95-…
  • CISA's deadline for US federal agencies: 2026-03-25 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Upgrade n8n to 1.120.4, 1.121.1 or 1.122.0 as stated in the description, and confirm the fix with the vendor advisory.
  2. Until upgraded, limit workflow creation and editing permissions to fully trusted users only.
  3. Run n8n in a hardened environment with restricted operating system privileges and limited network access.
  4. Review workflows, accounts and the host for signs of compromise, since the flaw is known to be exploited.
  5. Follow CISA's required action: apply vendor mitigations, follow BOD 22-01 guidance for cloud services, or discontinue use if mitigations are unavailable.

The record's structured data names no fixed version, though its description cites 1.120.4, 1.121.1 and 1.122.0. Check the vendor advisory to confirm. Until you can upgrade, restrict workflow creation and editing to fully trusted users and run n8n with restricted OS privileges and network access. These workarounds do not fully eliminate the risk. Follow CISA's required action.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-913 Improper Control of Dynamically-Managed Code Resources

Questions about CVE-2025-68613

Does an attacker need an account?
Yes. The attacker must be an authenticated user who can supply expressions during workflow configuration. Low privileges are enough, and no user interaction is needed.
Are the temporary mitigations enough?
No. Limiting workflow editing to trusted users and hardening the environment reduce risk but do not fully eliminate it. The vendor describes them as short-term measures only.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-03-11, with a US federal due date of 2026-03-25. Ransomware use is listed as unknown.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.