dbcve.org
N8nApplication

CVE-2026-27494

CRITICAL · 9.9 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 1.123.22 / 2.9.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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. Prior to versions 2.10.1, 2.9.3, and 1.123.22, an authenticated user with permission to create or modify workflows could use the Python Code node to escape the sandbox. The sandbox did not sufficiently restrict access to certain built-in Python objects, allowing an attacker to exfiltrate file contents or achieve RCE. On instances using internal Task Runners (default runner mode), this could result in full compromise of the n8n host. On instances using external Task Runners, the attacker might gain access to or impact other task executed on the Task Runner. Task Runners must be enabled using `N8N_RUNNERS_ENABLED=true`. The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to this version or later to remediate the vulnerability. 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 disable the Code node by adding `n8n-nodes-base.code` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation 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 confidence

The n8n workflow automation platform's Python Code node sandbox had insufficient restrictions on certain built-in Python objects, allowing authenticated users with workflow creation/modification permissions to escape the sandbox, achieve file exfiltration, and potentially execute arbitrary code. The impact varies based on Task Runner configuration - internal runners (default) allow full host compromise, while external runners enable access to other task executions.

MitigationUpgrade to n8n versions 2.10.1, 2.9.3, or 1.123.22 or later. If immediate upgrade is not feasible, restrict workflow creation/editing permissions to trusted users only and/or disable the Code node using the NODES_EXCLUDE environment variable.

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.123.22>= 2.0.0, < 2.9.3>= 2.10.0, < 2.10.1

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' from the command line, check the docker image tag, or inspect the package.json file in the n8n installation directory
    Affected if The installed version falls into any of these ranges: < 1.123.22, >= 2.0.0 and < 2.9.3, >= 2.10.0 and < 2.10.1
  2. Verify Python Code node is accessible
    Log into the n8n web interface and navigate to the nodes library or check if the Python Code node appears in the workflow editor node picker. Alternatively, check workflow configurations for nodes of type 'n8n-nodes-base.pythonCode'
    Affected if The Python Code node is available and can be added to workflows by users with workflow editing permissions
  3. Check Task Runner configuration
    Inspect the n8n configuration file (config.yaml or config.js) or environment variables for 'N8N_TASK_RUNNER_MODE' setting. Look for 'N8N_EXECUTOR_MODE' or 'N8N_TASK_RUNNER_EXECUTION_MODE' settings
    Affected if The Task Runner is configured in its default 'internal' mode (not explicitly set to 'external'), which allows full host compromise if the sandbox is escaped
  4. Review user role permissions for workflow editing
    Navigate to n8n Settings > Users & Permissions, or inspect the database table 'user_role' or equivalent. Identify which users or roles have 'workflow:create' or 'workflow:edit' permissions
    Affected if There exist users with workflow creation or modification permissions beyond trusted administrators, as this is required to exploit the sandbox escape

Your environment is affected if the n8n version is in the vulnerable ranges AND the Python Code node is accessible to users with workflow editing capabilities.

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 1.123.22 / 2.9.3 / 2.10.1 or later
Fixed in 1.123.222.9.32.10.1
Interim mitigation

Upgrade to n8n versions 2.10.1, 2.9.3, or 1.123.22 or later. If immediate upgrade is not feasible, restrict workflow creation/editing permissions to trusted users only and/or disable the Code node using the NODES_EXCLUDE environment variable.

Recommended fix High confidence

Upgrade to n8n version 1.123.22 (for 1.x users), 2.9.3 (for 2.0-2.9.x users), or 2.10.1 (for 2.10.x users)

  1. 1. Identify current n8n version by checking the container/service logs or running `n8n --version`
  2. 2. For n8n 1.x users: Upgrade to version 1.123.22 or later
  3. 3. For n8n 2.0.0 - 2.9.x users: Upgrade to version 2.9.3 or later
  4. 4. For n8n 2.10.x users: Upgrade to version 2.10.1 or later
  5. 5. If using Docker: Pull the new image (e.g., `docker pull n8nio/n8n:1.123.22` or `n8nio/n8n:2.10.1`) and recreate the container
  6. 6. If using npm: Run `npm install -g n8n@latest` or specify the version (e.g., `npm install -g [email protected]`)
  7. 7. Restart the n8n service after upgrade
  8. 8. Verify the upgrade was successful by checking the version and testing workflow execution

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

Fix this in N8n Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing10.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27494 — 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-2026-27494 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