dbcve.org
N8nApplication

CVE-2025-68668

CRITICAL · 9.9 CVSS v3.1 Published 2025-12-26
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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 · unedited
n8n is an open source workflow automation platform. From version 1.0.0 to before 2.0.0, a sandbox bypass vulnerability exists in the Python Code Node that uses Pyodide. An authenticated user with permission to create or modify workflows can exploit this vulnerability to execute arbitrary commands on the host system running n8n, using the same privileges as the n8n process. This issue has been patched in version 2.0.0. Workarounds for this issue involve disabling the Code Node by setting the environment variable NODES_EXCLUDE: "[\"n8n-nodes-base.code\"]", disabling Python support in the Code node by setting the environment variable N8N_PYTHON_ENABLED=false, which was introduced in n8n version 1.104.0, and configuring n8n to use the task runner based Python sandbox via the N8N_RUNNERS_ENABLED and N8N_NATIVE_PYTHON_RUNNER environment variables.

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 confidence

A sandbox bypass vulnerability in n8n's Python Code Node using Pyodide allows authenticated users with workflow creation/modification permissions to execute arbitrary commands on the host system with the same privileges as the n8n process. The vulnerability stems from insufficient isolation in the Pyodide-based sandbox implementation.

MitigationUpgrade to n8n version 2.0.0 or higher, or apply workarounds by setting NODES_EXCLUDE to disable the Code Node, N8N_PYTHON_ENABLED=false to disable Python support, or configure N8N_RUNNERS_ENABLED and N8N_NATIVE_PYTHON_RUNNER for task runner-based sandboxing.

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
N8nApplication
Affected:>= 1.0.0, < 2.0.0

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify n8n version
    Run 'n8n --version' or check the version in package.json, or inspect the running container/image tag
    Affected if Version is 1.x (greater than or equal to 1.0.0 but less than 2.0.0)
  2. Verify Python Code Node is not excluded
    Check if the Code node is excluded by inspecting environment variable NODES_EXCLUDE (should contain 'n8n-nodes-base.code' if disabled) or check active nodes in n8n UI
    Affected if NODES_EXCLUDE is not set or does not contain the Code node, meaning the node is available
  3. Confirm Python support is enabled
    Check environment variable N8N_PYTHON_ENABLED; if not set, Python is enabled by default in affected versions
    Affected if N8N_PYTHON_ENABLED is not set to 'false' or is absent, enabling Pyodide Python execution
  4. Verify task runner sandboxing is not configured
    Check if N8N_RUNNERS_ENABLED and N8N_NATIVE_PYTHON_RUNNER environment variables are set; absence means the older Pyodide sandbox is in use
    Affected if Neither N8N_RUNNERS_ENABLED nor N8N_NATIVE_PYTHON_RUNNER is configured, leaving the vulnerable Pyodide sandbox active
  5. Confirm user access to workflow creation/modification
    Review user roles and permissions in n8n to determine if any users have workflow create or edit rights
    Affected if Users exist with workflow creation or modification permissions, allowing access to the Code node

You are affected if running n8n version 1.x, the Code node is available, Python support is enabled (not disabled), and users with workflow edit permissions can access the Python Code node with the default Pyodide sandbox.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Vendor patch github.com →
Interim mitigation

Upgrade to n8n version 2.0.0 or higher, or apply workarounds by setting NODES_EXCLUDE to disable the Code Node, N8N_PYTHON_ENABLED=false to disable Python support, or configure N8N_RUNNERS_ENABLED and N8N_NATIVE_PYTHON_RUNNER for task runner-based sandboxing.

Recommended fix High confidence

n8n version 2.0.0

  1. 1. Back up your existing n8n installation, workflows, and database before upgrading
  2. 2. Stop the n8n service
  3. 3. Upgrade n8n to version 2.0.0 using your deployment method (e.g., Docker: docker pull n8nio/n8n:v2.0.0, npm: npm install -g [email protected], or your container orchestration tool)
  4. 4. Start the n8n service
  5. 5. Verify the upgrade was successful by checking the n8n version in the UI or CLI
  6. 6. Test that workflows with Python Code nodes function correctly in the updated version
Caveat Major version upgrades may include breaking changes; review n8n v2.0.0 release notes for migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68668 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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