CVE-2025-68613
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability requires an authenticated user to supply expressions during workflow configuration via the web interface, which are then evaluated insecurely. The malicious input looks like normal workflow configuration data, so a web application firewall cannot reliably distinguish attack requests from legitimate ones.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-68613 being exploited?
Yes. CVE-2025-68613 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-68613?
CVE-2025-68613 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-68613?
Yes. A fix has been recorded for CVE-2025-68613. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-68613 affect?
CVE-2025-68613 affects n8n:n8n. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 0.211.0 and < 1.120.4
- affected= 1.121.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Public exploit code: 1 Metasploit module · 37 GitHub proofs of concept · 1 Nuclei template
- exploit/multi/http/n8n_workflow_expression_rce · exploit · excellent
- n8n - Remote Code Execution via Expression Injection · detection template · critical
- wioui/n8n-CVE-2025-68613-exploit · 105 ★
- ZeroDayEvil/CVE-2026-21858-n8n-FullChain · 88 ★
- TheStingR/CVE-2025-68613-POC · 29 ★
- rxerium/CVE-2025-68613 · 27 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 3 Mar 2026 (SSVC 2.0.3).
timeline
- 19 Dec 2025Published
- 22 Dec 2025First public exploit or proof of concept · 2 days later
- 3 Mar 2026CISA SSVC assessment: exploitation active · 71 days (about 2 months) later
- 11 Mar 2026Added to CISA KEV (exploited in the wild) · 8 days later
- 12 Mar 2026CVE record last updated · 1 day later
- 25 Mar 2026CISA remediation due date (US federal agencies) · 13 days later
- 2 Nov 2026Analysed by vulneraibility.com · 223 days (about 7 months) later
also known as
- Advisoryakamai.com /blog/security-research/2026/feb/zerobot-malware-targets-n8n-automation-platform
- Linkgithub.com /n8n-io/n8n/security/advisories/GHSA-v98v-ff95-f3cp
- Linkgithub.com /n8n-io/n8n/commit/08f332015153decdda3c37ad4fcb9f7ba13a7c79
- Linkgithub.com /n8n-io/n8n/commit/1c933358acef527ff61466e53268b41a04be1000
- Linkgithub.com /n8n-io/n8n/commit/39a2d1d60edde89674ca96dcbb3eb076ffff6316
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-68613
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.