CVE-2025-68613 is a critical-severity (CVSS 9.9) CWE-913 vulnerability in n8n. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-03-11) — treat it as actively exploited and patch now. A fix is available for n8n — see the affected versions and patch details below.
n8n Vulnerable to Remote Code Execution via Expression Injection
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-03-11. Federal agencies were required to remediate by 2026-03-25.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-68613.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-68613 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
n8nnpmDescription
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | n8n | ≥ 0.211.0&&< 1.120.4 | 1.120.4npm install n8n@1.120.4 |
| 📦npm | n8n | ≥ 1.121.0&&< 1.121.1 | 1.121.1npm install n8n@1.121.1 |
Affected Products
n8nn8nResearch 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
ZeroDayEvil/CVE-2026-21858-n8n-FullChain
🛡️ Official AI Security Tool module for CVE-2026-21858 + CVE-2025-68613
TheStingR/CVE-2025-68613-POC
Public PoC + Scanner and research for CVE-2025-68613: Critical RCE in n8
rxerium/CVE-2025-68613
Detection for CVE-2025-68613
LingerANR/n8n-CVE-2025-68613
This laboratory provides a controlled environment to analyze and reprodu
hackersatyamrastogi/n8n-exploit-CVE-2025-68613-n8n-God-Mode-Ultimate
n8n God Mode Ultimate - CVE-2025-68613 Scanner v1.0.0 ║ ║
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n to 1.120.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-68613 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How to detect CVE-2025-68613
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2025-68613 -u https://target- Template
- n8n - Remote Code Execution via Expression Injection
- Severity
- critical
- Impact
- Authenticated attackers can execute arbitrary code with n8n process privileges, potentially leading to full system compromise.
- Remediation
- Upgrade to versions 1.120.4, 1.121.1, or 1.122.0 or later.
Template by ProjectDiscovery nuclei-templates (rxerium, PentesterFlow, MuhamadJuwandi), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2025-68613 in your dependencies?
Find it across npm, including transitive dependencies.