dbcve.org
N8nApplication

CVE-2026-49444

HIGH · 8.5 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 1.123.48 / 2.21.8 or later.
See remediation →
91/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 1.123.48, 2.21.8, and 2.22.4, an authenticated user with permission to create or modify workflows containing a Python Code Node could escape the sandbox and achieve arbitrary code execution on the task runner container. This vulnerability is fixed in 1.123.48, 2.21.8, and 2.22.4.

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

An authenticated n8n user with workflow creation/modification permissions can escape the Python sandbox in the Python Code Node and achieve arbitrary code execution on the task runner container. This allows privilege escalation from authenticated user to container-level RCE.

MitigationUpgrade n8n to version 1.123.48, 2.21.8, or 2.22.4. Additionally, restrict workflow creation/modification permissions to only trusted users and apply network segmentation to task runner containers.

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.48>= 2.0.0, < 2.21.8>= 2.22.0, < 2.22.4

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
Low
Availability
None

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

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. Determine installed n8n version
    Run `n8n --version` from the command line, check the Docker container tag, or inspect the package.json file in the n8n installation directory
    Affected if The version is < 1.123.48, or >= 2.0.0 and < 2.21.8, or >= 2.22.0 and < 2.22.4
  2. Verify Python Code Node is accessible
    Log into the n8n web interface and check if the Python Code node appears in the node palette, or query the /nodes endpoint of the n8n API
    Affected if The Python Code node is available and can be added to workflows
  3. Identify users with workflow modification permissions
    Check n8n user roles in the web UI under Settings > Users, or query the /users API endpoint. Look for roles that include workflow create/edit privileges such as 'Owner' or 'Editor'
    Affected if There are authenticated users with workflow creation or modification permissions enabled
  4. Confirm task runner containers are in use
    Check if n8n is configured with external task runners or if workflow execution uses containerized environments. Review n8n configuration files or the execution environment settings in the web UI
    Affected if Workflows execute in separate containers (task runners) rather than within the main n8n process

You are affected if your n8n version falls within any of the affected ranges AND the Python Code Node is accessible to users with workflow modification permissions in an environment using task runner containers.

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.48 / 2.21.8 / 2.22.4 or later
Fixed in 1.123.482.21.82.22.4
Interim mitigation

Upgrade n8n to version 1.123.48, 2.21.8, or 2.22.4. Additionally, restrict workflow creation/modification permissions to only trusted users and apply network segmentation to task runner containers.

Recommended fix High confidence

Upgrade to 1.123.48 (for 1.x users), 2.21.8 (for 2.0.0-2.21.x users), or 2.22.4 (for 2.22.0-2.22.3 users)

  1. Identify your current n8n version by checking the application or your deployment configuration
  2. If running version 1.x: Upgrade to version 1.123.48 or later
  3. If running version 2.0.0 - 2.21.x: Upgrade to version 2.21.8 or later
  4. If running version 2.22.0 - 2.22.3: Upgrade to version 2.22.4 or later
  5. After upgrading, verify the Python Code Node sandbox escape is no longer exploitable
  6. Review workflow executions to ensure no unauthorized access occurred during the vulnerable period
Caveat Review release notes for any breaking changes between your current version and the target upgrade version

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

Fix this in N8n Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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