CVE-2026-1470: Authenticated users can bypass the Expression sandbox mechanism to achieve full remote code execution on n8n’s main node.
Noroxi assessment
Priority: Plan (action score 45/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: 20.4% (FIRST EPSS); higher than 97.4% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: www.npmjs.com n8n 1.123.17, 2.4.5, 2.5.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to www.npmjs.com n8n 1.123.17, 2.4.5, 2.5.1 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 contains a critical Remote Code Execution (RCE) vulnerability in its workflow Expression evaluation system. Expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations.
- Published
- Jan 27, 2026
- Updated
- Jun 17, 2026
- EPSS
- 20.4% · 97th percentile
- CWE
- CWE-95
Report tools
Action score
45
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 6 / 30 · 20.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · JFROG
- 9.9
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
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.17
- n8n n8n2.0.0 and later · before 2.4.5
- n8n n8n2.5.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (JFROG). Independent of NVD's CPE analysis and usually ahead of it.
www.npmjs.com n8n
- before 1.123.17affected · semver
- 2.0.0 and later · before 2.4.5affected · semver
- 2.5.0 and later · before 2.5.1affected · semver
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.4.5 | 2.4.5 |
| npm | n8n | from 2.5.0 · before 2.5.1 | 2.5.1 |
| npm | n8n | before 1.123.17 | 1.123.17 |
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-2025-68668n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node43Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68949Jan 13, 2026 · n8n has a Webhook Node IP Whitelist Bypass via Partial String Matching21Monitor
- ← EarlierCVE-2026-0863Jan 18, 2026 · Sandbox escape in n8n Python task runner allows for arbitrary code execution on the underlying host.42Plan
- Later →CVE-2025-61917Feb 4, 2026 · n8n Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner30Monitor
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 |
|---|---|---|
| www.npmjs.com n8n | 1.123.17 | Vendor (CNA) |
| www.npmjs.com n8n | 2.4.5 | Vendor (CNA) |
| www.npmjs.com n8n | 2.5.1 | Vendor (CNA) |
| npm:n8n | 1.123.17 | Package registry (OSV) |
| npm:n8n | 2.4.5 | Package registry (OSV) |
| npm:n8n | 2.5.1 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-08639 days apartSandbox escape in n8n Python task runner allows for arbitrary code execution on the underlying host.42Plan
- CVE-2026-85165219 days apartn8n before 2.36.2 Expression Sandbox Bypass via SpreadElement28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0028 · Feb 9, 2026(n8n Otomasyon Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-95 · Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.