n8n up to 1.123.13/2.3.4/2.4.1 python-task-executor eval injection

Summaryinfo

A vulnerability categorized as critical has been discovered in n8n up to 1.123.13/2.3.4/2.4.1. Affected by this vulnerability is an unknown functionality of the component python-task-executor. The manipulation results in eval injection. This vulnerability was named CVE-2026-0863. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in n8n up to 1.123.13/2.3.4/2.4.1. Affected is an unknown functionality of the component python-task-executor. The manipulation with an unknown input leads to a eval injection vulnerability. CWE is classifying the issue as CWE-95. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval"). This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Using string formatting and exception handling, an attacker may bypass n8n's python-task-executor sandbox restrictions and run arbitrary unrestricted Python code in the underlying operating system. The vulnerability can be exploited via the Code block by an authenticated user with basic permissions and can lead to a full n8n instance takeover on instances operating under "Internal" execution mode. If the instance is operating under the "External" execution mode (ex. n8n's official Docker image) - arbitrary code execution occurs inside a Sidecar container and not the main node, which significantly reduces the vulnerability impact.

The advisory is shared for download at research.jfrog.com. This vulnerability is traded as CVE-2026-0863 since 01/12/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. There are neither technical details nor an exploit publicly available.

Upgrading to version 1.123.14, 2.3.5 or 2.4.2 eliminates this vulnerability. Applying the patch b73a4283cb14e0f27ce19692326f362c7bf3da02 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at EUVD (EUVD-2026-3171) and CERT Bund (WID-SEC-2026-0144). Once again VulDB remains the best source for vulnerability data.

Affected

• n8n n8n

Productinfo

Name

• n8n

Version

• 1.123.0
• 1.123.1
• 1.123.2
• 1.123.3
• 1.123.4
• 1.123.5
• 1.123.6
• 1.123.7
• 1.123.8
• 1.123.9
• 1.123.10
• 1.123.11
• 1.123.12
• 1.123.13
• 2.3.0
• 2.3.1
• 2.3.2
• 2.3.3
• 2.3.4
• 2.4.0
• 2.4.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion