Known exploited vulnerability

CVE-2025-68613

highCVSS 3.1 8.8In CISA KEVEPSS 99%Published · n8n-io

The short answer

CVE-2025-68613 affects n8n-io n8n and is rated high (CVSS 8.8). CISA added it to the Known Exploited Vulnerabilities catalog on 2026-03-11: attackers are using it, so patch it first. Fixed versions are published for n8n (1.120.4, 1.121.1).

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.

Weakness: CWE-913.

Severity

8.8 high

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploited (CISA KEV)

Yes, since Mar 11, 2026

Federal due date Mar 25, 2026

EPSS, next 30 days

99%

Higher than 100% of scored CVEs

How it can be exploited

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

What CISA says to do

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Affected packages and fixed versions

PackageEcosystemFixed inAdvisory
n8nnpm1.120.4, 1.121.1GHSA-v98v-ff95-f3cp

Is it in your code? Drop your lockfile into the free vulnerability check, or let vulnerability watch check your repository every day and open the upgrade as a pull request.

Affected products

n8n. NVD's record lists the exact affected versions.

References

Questions

Is CVE-2025-68613 being exploited?

Yes. CISA added CVE-2025-68613 to its Known Exploited Vulnerabilities catalog on 2026-03-11, with a federal remediation due date of 2026-03-25.

How do I fix CVE-2025-68613?

Upgrade to a fixed version: n8n (npm) 1.120.4 or 1.121.1. CISA's 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.

From NVD, CISA KEV, FIRST EPSS and OSV.dev, checked . Status on NVD: Analyzed. The description is NVD's text, quoted as published.

Related

Know the day a CVE lands in your code

Connect a GitHub repository and ZeusQA checks its dependencies daily, briefs each advisory and opens the fix. Three test runs free, no card.