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

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Yes, if you run n8n n8n. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2026-03-11, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2026-03-25; treat that as the outer limit, not the target.
• EPSS 99.0%, percentile 99.9: FIRST’s model estimates a 99.0% chance of exploitation activity in the next 30 days, higher than 99.9% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Needs an account (low (any account)). Exposure depends on who can log in.
• Only applies if your dependency tree includes n8n (npm) >= 0.211.0, < 1.120.4, fixed in 1.120.4; n8n (npm) >= 1.121.0, < 1.121.1, fixed in 1.121.1. Check your lockfile, including transitive dependencies.
• Editorial verdict: Act now. Ni8mare: n8n Unauthenticated Takeover, Plus a KEV RCE — If you self-host n8n and anything about it is reachable from the internet, upgrade today: one bug lets strangers in through public forms, and its companion RCE is on CISA's exploited list.

What it is

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.

From the GitHub advisory

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:

CISA’s summary

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

Weakness type: CWE-913.

Product: n8n n8n · Assigned by: GitHub_M · Published: 2025-12-19

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: low (any account)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: added 2026-03-11; federal due date 2026-03-25. Known ransomware use: Unknown.
• 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 SSVC assessment: exploitation active, automatable no, technical impact total.
• FIRST EPSS (model of 2026-10-21): 98.99% probability of exploitation activity in the next 30 days; percentile 99.9.

Timeline

• 2025-12-19 — CVE record published by GitHub_M
• 2025-12-22 — GitHub-reviewed advisory GHSA-v98v-ff95-f3cp published (critical)
• 2026-01-07 — erroneo.us brief: Ni8mare: n8n Unauthenticated Takeover, Plus a KEV RCE
• 2026-03-11 — Added to CISA’s Known Exploited Vulnerabilities catalog
• 2026-03-12 — CVE record last updated
• 2026-03-25 — CISA remediation deadline for US federal agencies

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. Listed in CISA KEV notes (github.com) github.com

Vulnerability records

1. GitHub Advisory GHSA-v98v-ff95-f3cp github.com
2. CVE.org record CVE-2025-68613 cve.org
3. NVD entry CVE-2025-68613 nvd.nist.gov

Government

1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com
3. github.com github.com
4. akamai.com akamai.com

All exploited n8n vulnerabilities · Critical npm advisories · Today’s Security Digest