Skip to main content
CVE-2026-0863VulnerabilityPublished Updated

CVE-2026-0863: n8n · Eval Injection

Affects n8nSource CVE Database V5

0

Not known to be exploited · CVSS 8.5 High · fixed in 2.4.2 : patch n8n soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
9.2% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.2, 2.3.5, 1.123.14
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade n8n to 2.4.2, 2.3.5 or 1.123.14.

Affected software

ProductAffectedFixed in
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • =0
  • =2.0.0
  • =2.4.0
Fixed in–
npmn8npkg:npm/n8nOther threatsAffected
  • >=2.4.0 <2.4.2
  • <1.123.14
  • >=2.0.0 <2.3.5
Fixed in
  • 2.4.2
  • 1.123.14
  • 2.3.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take the following specific mitigation steps: 1) Immediately identify and inventory all n8n instances, noting their execution mode (Internal vs External). 3) Enforce strict access controls and monitor authenticated users with basic permissions, as they can exploit this vulnerability. 4) For instances running in Internal mode, consider migrating to External execution mode to leverage container isolation and reduce risk. 5) Implement network segmentation and firewall rules to limit access to n8n instances only to trusted users and systems. 6) Enable comprehensive logging and monitoring of n8n activities to detect anomalous code execution attempts. 7) Conduct regular security assessments and penetration tests focusing on automation platforms. 8) Educate developers and administrators about the risks of dynamic code evaluation and sandbox bypass techniques. 9) Review and harden container security policies if using External mode to prevent container breakout. 10) Prepare incident response plans specifically addressing potential automation platform compromises.

Description

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.

References

Community reviews

Loading reviews…