How severe is CVE-2025-68613?

CVE-2025-68613 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-68613?

CVE-2025-68613 affects the following packages: n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix CVE-2025-68613?

Update n8n to version 1.120.4 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2025-68613 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2025-68613, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-68613?

CVE-2025-68613 has an EPSS (Exploit Prediction Scoring System) score of 68.3%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-68613 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-68613 (n8n Improper Control of Dynamically-Managed Code Resources Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-03-11. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-03-25. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-68613?

CVE-2025-68613 is classified as CWE-913 (CWE-913). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2025-68613?

A Nuclei detection template exists for CVE-2025-68613, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-68613 published, and has it been updated?

CVE-2025-68613 was published on December 19, 2025 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-03-11 — agencies required to remediate by 2026-03-25

📦 npm

CVE-2025-68613

CRITICAL

n8n Vulnerable to Remote Code Execution via Expression Injection

Also known asGHSA-v98v-ff95-f3cp

Published

Dec 19, 2025

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

68.3%probability of exploitation in next 30 days

High Risk99th percentile+2.55%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

📦n8n📦n8n

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	≥ 0.211.0&&< 1.120.4	1.120.4
📦npm	`n8n`	≥ 1.121.0&&< 1.121.1	1.121.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

wioui/n8n-CVE-2025-68613-exploit

CVE-2025-68613: n8n RCE vulnerability exploit and documentation

⭐ 98🍴 22Jun 2026

rxerium/CVE-2025-68613

Detection for CVE-2025-68613

⭐ 29🍴 3Mar 2026

TheStingR/CVE-2025-68613-POC

Public PoC + Scanner and research for CVE-2025-68613: Critical RCE in n8

⭐ 25🍴 0May 2026

LingerANR/n8n-CVE-2025-68613

This laboratory provides a controlled environment to analyze and reprodu

⭐ 7🍴 0Jan 2026

hackersatyamrastogi/n8n-exploit-CVE-2025-68613-n8n-God-Mode-Ultimate

n8n God Mode Ultimate - CVE-2025-68613 Scanner v1.0.0 ║ ║

⭐ 5🍴 3Apr 2026

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-68613 in your stack?

O3 detects CVE-2025-68613 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works