CVE-2026-27494

CRITICALNVD 9.99.9
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

n8n is an open source workflow automation platform. Prior to versions 2.10.1, 2.9.3, and 1.123.22, an authenticated user with permission to create or modify workflows could use the Python Code node to escape the sandbox. The sandbox did not sufficiently restrict access to certain built-in Python objects, allowing an attacker to exfiltrate file contents or achieve RCE. On instances using internal Task Runners (default runner mode), this could result in full compromise of the n8n host. On instances using external Task Runners, the attacker might gain access to or impact other task executed on the Task Runner. Task Runners must be enabled using N8N_RUNNERS_ENABLED=true. The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to this version or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations. Limit workflow creation and editing permissions to fully trusted users only., and/or disable the Code node by adding n8n-nodes-base.code to the NODES_EXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

CVSS v3
9.9
EG Score
9.9(low)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

February 25, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Jul 27, 2026
Patch available. Sources: github_release, github.
github Patch Available

Python Code Node Sandbox Escape · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-mmgg-m5j7-f83h
github_release Patch Available

[email protected]

Patch available: n8n-io/n8n [email protected]

https://github.com/n8n-io/n8n/releases/tag/[email protected]
github_release Patch Available

[email protected]

Patch available: n8n-io/n8n [email protected] (pre-release)

https://github.com/n8n-io/n8n/releases/tag/[email protected]
github_release Patch Available

[email protected]

Patch available: n8n-io/n8n [email protected]

https://github.com/n8n-io/n8n/releases/tag/[email protected]

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 2× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:04 UTCEG score recompute
  2. 2026-07-27 13:57 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-27494?
CVE-2026-27494 is a critical vulnerability published on February 25, 2026. n8n is an open source workflow automation platform. Prior to versions 2.10.1, 2.9.3, and 1.123.22, an authenticated user with permission to create or modify workflows could use the Python Code node to escape the sandbox. The sandbox did not sufficiently restrict access to certain built-in Python…
When was CVE-2026-27494 disclosed?
CVE-2026-27494 was first published in the National Vulnerability Database on February 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27494 actively exploited?
CVE-2026-27494 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.3% of all scored CVEs.
What is the CVSS score of CVE-2026-27494?
CVE-2026-27494 has a CVSS v3 base score of 9.9 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-27494?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27494, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-27494

Explore →

Is Your Infrastructure Affected by CVE-2026-27494?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs