Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-27494— n8n has Arbitrary File Read via Python Code Node Sandbox Escape

Quick assessment

Affected
n8n-io n8n
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

n8n是n8n开源的一个可扩展的工作流自动化工具。 n8n 2.10.1之前版本、2.9.3之前版本和1.123.22之前版本存在安全漏洞,该漏洞源于Python Code节点的沙箱未充分限制对某些内置Python对象的访问,可能导致具有工作流创建或修改权限的经过身份验证的用户实现沙箱逃逸。

AI Predicted 9.8 Difficulty: Easy EPSS 0.64% · P49

Possible ATT&CK Techniques 1 AI

T1059 · Command and Scripting Interpreter
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-27494

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
n8n has Arbitrary File Read via Python Code Node Sandbox Escape
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
将系统数据暴露到未授权控制的范围
Source: CVE Program / CVE List V5
Vulnerability Title
n8n 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
n8n是n8n开源的一个可扩展的工作流自动化工具。 n8n 2.10.1之前版本、2.9.3之前版本和1.123.22之前版本存在安全漏洞,该漏洞源于Python Code节点的沙箱未充分限制对某些内置Python对象的访问,可能导致具有工作流创建或修改权限的经过身份验证的用户实现沙箱逃逸。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
n8n-io n8n < 1.123.22 -

II. Public POCs for CVE-2026-27494

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-27494

请登录查看更多情报信息。

Same Patch Batch · n8n-io · 2026-02-25 · 7 CVEs total

CVE-2026-27577 9.4 CRITICAL n8n: Expression Sandbox Escape Leads to RCE
CVE-2026-27495 n8n has a Sandbox Escape in its JavaScript Task Runner
CVE-2026-27493 n8n has Unauthenticated Expression Evaluation via Form Node
CVE-2026-27497 n8n has Potential Remote Code Execution via Merge Node
CVE-2026-27578 n8n Vulnerable to Stored XSS via Various Nodes
CVE-2026-27498 n8n has Arbitrary Command Execution via File Write and Git Operations

IV. Related Vulnerabilities

V. Comments for CVE-2026-27494

No comments yet


Leave a comment