CVE-2026-27493: n8n has Unauthenticated Expression Evaluation via Form Node
Noroxi assessment
Priority: Monitor (action score 38/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 72.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: n8n (npm) 2.9.3, 2.10.1, 1.123.22.
Low priority for now. Upgrade to n8n (npm) 2.9.3, 2.10.1, 1.123.22 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 1.3% · 72th percentile
- CWE
- CWE-94
Report tools
Action score
38
Low priority for now.
- CVSS
- 38 / 40 · 9.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 9.5
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| n8n | n8n | cpe:2.3:a:n8n:n8n |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
n8n-io n8n
- < 1.123.22, >= 2.0.0, < 2.9.3, >= 2.10.0, < 2.10.1affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- n8n n8nbefore 1.123.22
- n8n n8n2.0.0 and later · before 2.9.3
- n8n n8n2.10.0 and later · before 2.10.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | n8n | from 2.0.0 · before 2.9.3 | 2.9.3 |
| npm | n8n | from 2.10.0 · before 2.10.1 | 2.10.1 |
| npm | n8n | before 1.123.22 | 1.123.22 |
Same product
n8n: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-68613n8n Vulnerable to Remote Code Execution via Expression InjectionKEV95Now
- CVE-2026-21858n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling63This week
- CVE-2026-1470Authenticated users can bypass the Expression sandbox mechanism to achieve full remote code execution on n8n’s main node.45Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-21893Feb 4, 2026 · n8n Vulnerable to Command Injection in Community Package Installation37Monitor
- ← EarlierCVE-2026-25631Feb 6, 2026 · Domain allowlist bypass enables credential exfiltration21Monitor
- Later →CVE-2026-27494Feb 25, 2026 · n8n has Arbitrary File Read via Python Code Node Sandbox Escape28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:n8n | 1.123.22 | Package registry (OSV) |
| npm:n8n | 2.10.1 | Package registry (OSV) |
| npm:n8n | 2.9.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-2187749 days apartn8n is vulnerable to Remote Code Execution via Arbitrary File Write41Plan
- CVE-2026-275770 days apartn8n: Expression Sandbox Escape Leads to RCE40Plan
- CVE-2026-274950 days apartn8n has a Sandbox Escape in its JavaScript Task Runner37Monitor
- CVE-2026-3366028 days apartn8n Has Multiple Remote Code Execution Vulnerabilities in Merge Node AlaSQL SQL Mode37Monitor
- CVE-2026-274980 days apartn8n has Arbitrary Command Execution via File Write and Git Operations36Monitor
- CVE-2026-72765167 days apartn8n before 2.32.1 Remote Code Execution via Expression Sandbox Escape34Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.