Skip to content
Blog

n8n Sandbox Escape Vulnerability (CVE-2026-42234) — High Severity

N8N-Banner-ucartz
In this article
  1. CVE Details
  2. Affected Products
  3. Current Status
  4. Severity Level
  5. Possible Solutions
  6. References

n8n, a popular open-source platform for automating workflows, recently disclosed a significant security flaw. This vulnerability could allow an authenticated user to bypass security restrictions within the Python Code Node, potentially leading to unauthorized execution of commands on the system where n8n workflows run. This is a serious concern, especially for installations that utilize the Python Task Runner feature, and highlights the critical need for prompt updates.

CVE Details

  • Product Name: n8n
  • Published Date: May 04, 2026
  • Severity: High (CVSS Score 8.8)
  • Status: Analyzed

Affected Products

The following versions of n8n are known to be affected by this sandbox escape vulnerability:

  • n8n versions prior to 1.123.32
  • n8n versions prior to 2.17.4
  • n8n versions prior to 2.18.1

Current Status

This vulnerability has been thoroughly analyzed and publicly disclosed. Patches are available to address the issue, and users are strongly advised to update their systems.

Severity Level

This vulnerability is rated as High severity, with a CVSS score of 8.8. A High severity rating indicates that exploiting this flaw could have a severe impact on the confidentiality and integrity of the affected system. Specifically, an attacker with low privileges could gain significant control over the n8n task runner environment, potentially compromising sensitive data or disrupting operations.

Possible Solutions

The good news is that n8n has already released patches to address this critical issue. Users should upgrade their n8n installations to one of the following versions or later to ensure their systems are secure:

  • n8n version 1.123.32
  • n8n version 2.17.4
  • n8n version 2.18.1

If an immediate upgrade is not feasible, temporary mitigation steps can be considered, though these do not offer complete protection and should only be used as a short-term measure:

  • Limit Permissions: Restrict workflow creation and editing permissions to only fully trusted administrative users within your n8n environment.
  • Disable Python Code Node: You can disable the Python Code node by setting the NODES_EXCLUDE environment variable to include n8n-nodes-base.code.
  • Disable Python Task Runner: If your workflows do not rely on Python functionality, consider disabling the Python Task Runner entirely.

These workarounds offer a temporary reduction in risk but do not fully resolve the underlying vulnerability. Upgrading to a patched version is the most secure and recommended solution.

References

  • https://github.com/n8n-io/n8n/security/advisories/GHSA-44v6-jhgm-p3m4
Share
Alex Joseph

Alex Joseph

Alex Joseph is a Senior Support Staff professional with deep experience in server management, web hosting technologies, and cybersecurity operations. He works daily with Linux servers, cloud platforms, performance tuning, and security hardening, giving him strong real-world technical knowledge. Along with his support role, he write about security best practices, hosting infrastructure, and software management.

Related updates

Start Building Today

Ready to Get Started?

VPS, dedicated servers, streaming and managed hosting with 24/7 support from the Ucartz team.