Quick answers
- Is CVE-2025-68668 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-68668 being exploited in the wild.
- How severe is CVE-2025-68668?
- Critical severity, with a CVSS score of 9.9, published 26 December 2025.
- Which products and versions are affected?
- N8n 1.0.0 to 1.x; patched in 2.0.0.
- Is there a fix for CVE-2025-68668?
- A patch was published on 2.0.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-68668 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-68668?
- Check whether you run N8n at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A sandbox escape exists in the Pyodide-based Python Code Node implementation that allows authenticated users to break out of the intended Python sandbox. The vulnerability affects n8n versions 1.0.0 through 1.x, where Pyodide is used for Python code isolation. An attacker with permission to create or modify workflows can execute arbitrary commands on the host system with the same privileges as the n8n process. The vulnerability was addressed in n8n 2.0.0 by introducing a task-runner-based native Python implementation as the default (optional in version 1.111.0+). Workarounds include disabling the Code Node entirely, disabling Python support, or enabling the secure task-runner sandbox.
Affected products
- n8n n8n 1.0.0 to 1.x; patched in 2.0.0
Identifiers
- CVE-2025-68668
- GHSA-62r4-hw23-cc8v
Timeline
- 2025-12-24: disclosed
- 2.0.0: patched