CVE-2025-68668: n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node

Should you act?

High exploit likelihood

EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 13.2%, percentile 96: FIRST’s model estimates a 13.2% chance of exploitation activity in the next 30 days, higher than 96% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Needs an account (low (any account)). Exposure depends on who can log in.
• Only applies if your dependency tree includes n8n (npm) >= 1.0.0, < 2.0.0, fixed in 2.0.0. Check your lockfile, including transitive dependencies.

What it is

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 NODESEXCLUDE: "[\"n8n-nodes-base.code\"]", disabling Python support in the Code node by setting the environment variable N8NPYTHONENABLED=false, which was introduced in n8n version 1.104.0, and configuring n8n to use the task runner based Python sandbox via the N8NRUNNERSENABLED and N8NNATIVEPYTHONRUNNER environment variables.

From the GitHub advisory

Impact 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.

Patches In n8n version 1.111.0, a task-runner-based native Python implementation was introduced as an optional feature, providing a more secure isolation model.

To enable it, you need to configure the N8NRUNNERSENABLED and N8NNATIVEPYTHONRUNNER environment variables.

This implementation became the default starting with n8n version 2.0.0.

Weakness type: CWE-693.

Product: n8n (npm) · Assigned by: GitHub_M · Published: 2025-12-26

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: low (any account)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable no, technical impact total.
• FIRST EPSS (model of 2026-10-21): 13.17% probability of exploitation activity in the next 30 days; percentile 96.

Timeline

• 2025-12-26 — CVE record published by GitHub_M
• 2025-12-26 — GitHub-reviewed advisory GHSA-62r4-hw23-cc8v published (critical)
• 2026-01-05 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-62r4-hw23-cc8v github.com
2. CVE.org record CVE-2025-68668 cve.org
3. NVD entry CVE-2025-68668 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. smartkeyss.com smartkeyss.com

Critical npm advisories · Today’s Security Digest