# CVE-2026-1470: n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution

> Authenticated attackers can bypass the Expression sandbox in n8n to execute arbitrary code, leading to full system compromise.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-5xrp-6693-jjx9

## What is CVE-2026-1470?

CVE-2026-1470 is a critical code injection vulnerability in N8n N8n, published on 27 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2026-1470?

6 open source packages ship an affected version, including n8n. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `n8n` | npm | All versions | 1.123.17 |
| `n8n` | npm | All versions | 1.123.17 |
| `n8n` | npm | From 2.0.0 | 2.4.5 |
| `n8n` | npm | From 2.0.0 | 2.4.5 |
| `n8n` | npm | From 2.5.0 | 2.5.1 |
| `n8n` | npm | From 2.5.0 | 2.5.1 |

Products: N8n N8n.

## How do I fix CVE-2026-1470?

Upgrade n8n to a fixed version for your release line: 1.123.17, 2.4.5 or 2.5.1.

## Is CVE-2026-1470 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1470 exists.

## Other vulnerabilities in N8n N8n

- [CVE-2025-68613](https://insights.sbomify.com/CVE-2025-68613/): n8n Improper Control of Dynamically-Managed Code Resources (critical 10.0, exploited in the wild)
- [CVE-2026-21877](https://insights.sbomify.com/CVE-2026-21877/): n8n is vulnerable to Remote Code Execution via Arbitrary File Write (critical 10.0)
- [CVE-2026-21858](https://insights.sbomify.com/CVE-2026-21858/): n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling (critical 10.0)
- [CVE-2025-68668](https://insights.sbomify.com/CVE-2025-68668/): n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node (critical 9.9)
- [CVE-2026-27493](https://insights.sbomify.com/CVE-2026-27493/): n8n has Unauthenticated Expression Evaluation via Form Node (critical 9.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1470 and fix it if it is affected.

What it is: CVE-2026-1470 is a critical code injection vulnerability in N8n N8n, published on 27 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1470 exists.

Affected packages and fixed versions:
- n8n (npm): affected all versions; fixed in 1.123.17
- n8n (npm): affected all versions; fixed in 1.123.17
- n8n (npm): affected from 2.0.0; fixed in 2.4.5
- n8n (npm): affected from 2.0.0; fixed in 2.4.5
- n8n (npm): affected from 2.5.0; fixed in 2.5.1
- n8n (npm): affected from 2.5.0; fixed in 2.5.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1470/ (Markdown: https://insights.sbomify.com/CVE-2026-1470/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1470
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1470
- OSV: https://osv.dev/vulnerability/CVE-2026-1470

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1470/
Summaries are generated and may contain mistakes; the official description above is the record.