What is the CVSS score of CVE-2026-27495?

CVE-2026-27495 has a CVSS 3.1 base score of 9.9 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

How to fix or mitigate CVE-2026-27495?

Within 24 hours: Inventory all n8n deployments and identify which versions are running (check if below 1.123.22, 2.9.3, or 2.10.1). Restrict workflow creation/modification permissions to only essential administrators and audit recent workflow changes for suspicious activity. Within 7 days: Implement network segmentation to isolate n8n instances and their connected systems; deploy enhanced logging and monitoring on n8n instances for unusual code execution patterns. Within 30 days: Upgrade to patched versions (1.123.22, 2.9.3, or 2.10.1 or later) once available, or migrate to alternative workflow automation platforms if upgrade timeline is uncertain.

N8n CVE-2026-27495

CRITICAL

Code Injection (CWE-94)

2026-02-25 security-advisories@github.com

GHSA-jjpj-p2wh-qf23

RCE Code Injection AI / ML N8n

9.9

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Authenticated user creates workflow
Exploit

Inject malicious JavaScript in Task Runner
Execution

Escape sandbox boundary
Impact

Execute arbitrary code on host system

Vulnerability Assessment

Weakness	CWE CWE-94 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Code injection prevention, sandbox exec MITRE ATT&CK 2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Authenticated user account with workflow creation/modification permissions required. Task Runners must be explicitly enabled via N8N_RUNNERS_ENABLED=true environment variable. Vulnerability affects n8n versions before 2.10.1, 2.9.3, and 1.123.22.
Impact	CVSS 9.9 with scope change. Part of a cluster of n8n critical CVEs — multiple independent code execution paths.
Exploit ScenarioDerived	User with workflow permissions crafts malicious expression that executes arbitrary code, accessing all integrated service credentials.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Code injection in n8n workflow automation before 2.10.1/2.9.3/1.123.22 allows authenticated users to execute arbitrary code by creating or editing workflows with malicious expressions. Third n8n RCE CVE in this release.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:55 CVSS 9.9

Code injection via workflow expressions in n8n.

RemediationAI

Update n8n to patched version.

Affected Packages

npm n8n fix: 1.123.22, 2.9.3, 2.10.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-94 in n8n workflow platform. Authenticated users with workflow edit permissions can inject code through expression evaluation.

Know when N8n gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.9 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

CVE Published

Feb 25, 2026 - 23:16 nvd

CRITICAL 9.9

DescriptionGitHub Advisory

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 exploit a vulnerability in the JavaScript Task Runner sandbox to execute arbitrary code outside the sandbox boundary. 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 one of these versions 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 use external runner mode (N8N_RUNNERS_MODE=external) to limit the blast radius. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Executive ViewAI

Why It Matters

A critical vulnerability in n8n workflow automation platform allows authenticated users to bypass security controls and execute arbitrary code on affected systems. This poses a severe risk to any organization using n8n, as internal users or compromised accounts could gain unauthorized access to sensitive data and critical infrastructure connected through workflows.

Business Impact: Severe

Compensating Controls

Disable JavaScript Task Runner functionality if not business-critical; restrict workflow creation permissions to a minimal set of trusted administrators with MFA; isolate n8n instances on segmented networks with strict egress controls; implement runtime behavior monitoring and code execution detection tools; maintain detailed audit logs of all workflow modifications and executions; consider air-gapping n8n from production systems until patch is available.

Threat Intelligence Overview

EPSS Score

0.1%

Top 77% exploitable

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC No

EPSS 0.1%

Patch available Yes

Active threat No

Deciding rule

CRITICAL severity

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Open

Automatable· derived

Human Impact

Very High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +50

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution CRITICAL

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.