cve.bz

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

8.8 highKEVExploitEPSS 99%Fix available

High (8.8) in n8n n8n. In CISA KEV since 2026-03-11. EPSS 99% estimated probability of exploitation activity in the next 30 days. Fixed in n8n 1.120.4, 1.121.1.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
99% (unchanged from 99% a week ago; 99% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-03-11, due 2026-03-25
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2026-03-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-913 Improper Control of Dynamically-Managed Code Resources
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-68613 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68613?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68613?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68613 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
n8n:n8nfrom 0.211.0 before 1.120.4
n8n:n8n1.121.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v98v-ff95-f3cpnpmn8n>=0.211.0 <1.120.41.120.4
GHSA-v98v-ff95-f3cpnpmn8n>=1.121.0 <1.121.11.121.1

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

30 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

References

Check your stackJSON