CVE
CVE-2026-27493
n8n-io · n8n
- First Reported
- Mar 11, 2026
- Latest Reported
- Mar 11, 2026
CVE Enrichment
- CVSS
- 9.5 CRITICAL
- EPSS
- 1.39%
- EPSS Percentile
- 72.40%
- CISA KEV
- Not listed
Description
n8n is an open source workflow automation platform. Prior to versions 2.10.1, 2.9.3, and 1.123.22, a second-order expression injection vulnerability existed in n8n's Form nodes that could allow an unauthenticated attacker to inject and evaluate arbitrary n8n expressions by submitting crafted form data. When chained with an expression sandbox escape, this could escalate to remote code execution on the n8n host. The vulnerability requires a specific workflow configuration to be exploitable. First, a form node with a field interpolating a value provided by an unauthenticated user, e.g. a form submitted value. Second, the field value must begin with an `=` character, which caused n8n to treat it as an expression and triggered a double-evaluation of the field content. There is no practical reason for a workflow designer to prefix a field with `=` intentionally — the character is not rendered in the output, so the result would not match the designer's expectations. If added accidentally, it would be noticeable and very unlikely to persist. An unauthenticated attacker would need to either know about this specific circumstance on a target instance or discover a matching form by chance. Even when the preconditions are met, the expression injection alone is limited to data accessible within the n8n expression context. Escalation to remote code execution requires chaining with a separate sandbox escape vulnerability. 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. Review usage of form nodes manually for above mentioned preconditions, disable the Form node by adding `n8n-nodes-base.form` to the `NODES_EXCLUDE` environment variable, and/or disable the Form Trigger node by adding `n8n-nodes-base.formTrigger` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Technical Details
- CVSS Version
- 4.0
- CNA / NVD Source
- [email protected]
- Published
- 26-Feb-2026 06:16
- Last Modified
- 17-Jun-2026 17:27
- EPSS Date
- 2026-11-08
- CWE
- CWE-94, CWE-95
CVSS Vector
CVSS:4.0 AV:N /
AC:L /
AT:P /
PR:N /
UI:N /
VC:H /
VI:H /
VA:H /
SC:H /
SI:H /
SA:H /
E:X /
CR:X /
IR:X /
AR:X /
MAV:X /
MAC:X /
MAT:X /
MPR:X /
MUI:X /
MVC:X /
MVI:X /
MVA:X /
MSC:X /
MSI:X /
MSA:X /
S:X /
AU:X /
R:X /
V:X /
RE:X /
U:X
CNA Products / Version Status
- n8n-io · n8n
Source: CNA · [email protected]
Default status: unknown
< 1.123.22 — affected
>= 2.0.0, < 2.9.3 — affected
>= 2.10.0, < 2.10.1 — affected
Affected Products / Versions
- n8n / n8n
Source: NVD CPE · affected
Version / affected range: * · before (exclusive) 1.123.22
cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:* - n8n / n8n
Source: NVD CPE · affected
Version / affected range: * · from (inclusive) 2.0.0 · before (exclusive) 2.9.3
cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:* - n8n / n8n
Source: NVD CPE · affected
Version / affected range: * · from (inclusive) 2.10.0 · before (exclusive) 2.10.1
cpe:2.3:a:n8n:n8n:*:*:*:*:*:node.js:*:*
References
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (1)
- Two critical bugs—CVE-2026-27577 (sandbox escape leading to RCE) and CVE-2026-27493 (unauthenticated expression evaluation via Form nodes)—were disclosed and patched. Critical n8n Flaws Could Enable Remote Code Execution and Credential Exposure
CVE (3)
People (1)
MITRE ATT&CK (3)
Products (1)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
