Threadlinqs IntelligenceStart free

VulnerabilityCVE-2025-68668Published 2025-12-26

CVE-2025-68668 — N8n

criticalPublic exploit1 PoC repo

As of 2026-02-04, CVE-2025-68668 is a CRITICAL-severity vulnerability in N8n, CVSS v3.1 9.9, EPSS 13.1% (96.2th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2025-68668, most recently “n8n Multi-CVE Vulnerability Cascade — Expression Sandbox Escape, Pyodide RCE, Arbitrary File Write, Command Injection (9 CVEs, 2× CVSS 10.0)”.

CVSS v3.1
9.9/10Critical
EPSS
13.1%Higher than 96.2% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
10/10Threadlinqs triage score
Published
Updated 2026-02-04
CVSS v3.1 9.9 (CRITICAL) · EPSS 13.1% (higher than 96.2% of all scored CVEs) · Priority 10/10 · Published 2025-12-26

Last updated:

What is CVE-2025-68668?

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.

The record classifies CVE-2025-68668 under weakness class CWE-693. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 328 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.9 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
EPSS (FIRST)
13.1% probability of exploitation in the next 30 days, higher than 96.2% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
10/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2025-12-26

Is CVE-2025-68668 being exploited?

Weaponised exploit code for CVE-2025-68668 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 37 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2025-68668

The record marks a vendor fix as available for CVE-2025-68668. Patch reference: https://github.com/n8n-io/n8n/security/advisories/GHSA-62r4-hw23-cc8v. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2025-68668

1 tracked threat in the Threadlinqs corpus references CVE-2025-68668, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories.

Vendor advisory and patch

Other references