Skip to main content
VulnerabilityPublished Updated

CVE-2025-68668: n8n · Protection Mechanism Failure

Affects n8nSource CVE Database V5

0

Not known to be exploited · 13% EPSS · CVSS 9.9 Critical : upgrade to 2.0.0 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
13.1% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Dec 2025

  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 26 Oct 2026.

What to do

Upgrade n8n-io/n8n to 2.0.0.

Affected software

ProductAffectedFixed in
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <2.0.0
Fixed in
  • 2.0.0

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 immediately upgrade n8n to version 2.0.0 or later to fully remediate this vulnerability. If immediate upgrading is not feasible, apply the following mitigations: disable the Python Code Node by setting the environment variable NODES_EXCLUDE to exclude "n8n-nodes-base.code"; disable Python support in the Code Node by setting N8N_PYTHON_ENABLED=false (available since version 1.104.0); configure n8n to use the task runner-based Python sandbox by enabling N8N_RUNNERS_ENABLED and N8N_NATIVE_PYTHON_RUNNER environment variables. Additionally, restrict workflow creation and modification permissions to trusted users only, implement strong authentication and access controls, and monitor workflow changes and system logs for suspicious activity. Network segmentation and limiting access to the n8n management interface can reduce exposure. Regularly audit deployed n8n versions and configurations to ensure compliance with security best practices.

Description

n8n is an open source workflow automation platform. From version 1.0.0 to before 2.0.0, a sandbox bypass vulnerability exists in the Python Code Node that uses Pyodide. An authenticated user with permission to create or modify workflows can exploit this vulnerability to execute arbitrary commands on the host system running n8n, using the same privileges as the n8n process. This issue has been patched in version 2.0.0. Workarounds for this issue involve disabling the Code Node by setting the environment variable NODES_EXCLUDE: "[\"n8n-nodes-base.code\"]", disabling Python support in the Code node by setting the environment variable N8N_PYTHON_ENABLED=false, which was introduced in n8n version 1.104.0, and configuring n8n to use the task runner based Python sandbox via the N8N_RUNNERS_ENABLED and N8N_NATIVE_PYTHON_RUNNER environment variables.

References

Community reviews

Loading reviews…