CVE-2025-68613
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedn8n 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencen8n workflow automation platform versions 0.211.0 through 1.120.3/1.121.0 contain a critical RCE vulnerability in the workflow expression evaluation system. Authenticated users can supply malicious expressions that are evaluated in an insufficiently isolated execution context, allowing arbitrary code execution with n8n process privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 0.211.0, < 1.120.4= 1.121.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed n8n versionRun `n8n --version` from the command line, check the package.json file in the n8n installation directory, or query the n8n API endpoint `/rest/version` if accessibleAffected if The version is 0.211.0 through 1.120.3, or exactly 1.121.0
-
Verify user access to workflow editingReview user roles and permissions in n8n under Settings > Users or by querying the API endpoint `/rest/users` to determine which users can create or edit workflowsAffected if Any non-admin or untrusted user account has workflow create or edit permissions
-
Check if expression-based nodes are in useExamine existing workflows in the n8n UI or via the API endpoint `/rest/workflows` to identify workflows that contain expressions in node parameters (typically using {{...}} syntax)Affected if Workflows contain expressions that could be manipulated by authenticated users
-
Confirm n8n process privilegesCheck the operating system user running the n8n process and its permissions using commands like `ps aux | grep n8n` or system service configuration filesAffected if The n8n process runs with root or elevated OS privileges rather than a restricted service account
A user is affected if their n8n version falls within 0.211.0 to 1.120.3 or equals 1.121.0 AND authenticated users have the ability to create or edit workflows containing expressions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.120.4
Upgrade immediately to version 1.120.4, 1.121.1, or 1.122.0 which introduces additional safeguards to restrict expression evaluation. If immediate upgrade is not feasible, restrict workflow creation/editing to trusted users only and deploy n8n in a hardened environment with limited OS privileges.
1.120.4, 1.121.1, or 1.122.0 (or latest stable)
- Back up your n8n instance including workflows, credentials, and database before proceeding
- Upgrade n8n to version 1.120.4, 1.121.1, or 1.122.0 (or later stable release)
- Verify the upgrade was successful by checking the n8n version
- Test that existing workflows function correctly after the upgrade
- Review and limit workflow creation and editing permissions to trusted users only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-68613 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data