Critical n8n vulnerability: CVE-2026-1470 allows remote code execution
Critical n8n vulnerability: CVE-2026-1470 allows remote code execution
A critical security vulnerability has been disclosed in n8n, the popular workflow automation platform. CVE-2026-1470 has a CVSS score of 10.0 (the maximum) and allows authenticated users to execute arbitrary code on the server.
If you're running n8n, you need to update immediately.
The short version
| Detail | Value |
|---|---|
| CVE ID | CVE-2026-1470 |
| GHSA ID | GHSA-5xrp-6693-jjx9 |
| Severity | Critical (CVSS 10.0) |
| Vulnerability Type | Remote Code Execution (Eval Injection) |
| Affected Versions | < 1.123.17, 2.0.0 - 2.4.4, 2.5.0 |
| Patched Versions | 1.123.17, 2.4.5, 2.5.1 |
Action required: Update n8n to a patched version now.
What's the vulnerability?
The flaw exists in n8n's workflow expression evaluation system. When users configure workflows, they can use expressions to dynamically reference data. The problem is that these expressions are evaluated in an execution context that isn't sufficiently isolated from the underlying runtime.
In plain terms: an authenticated user can craft a malicious expression that escapes the sandbox and executes arbitrary code with the privileges of the n8n process.
This is classified as CWE-95: Improper Neutralization of Directives in Dynamically Evaluated Code, also known as "Eval Injection."
Why this is serious
The CVSS 3.1 score breaks down like this:
- Attack Vector: Network (can be exploited remotely)
- Attack Complexity: Low (easy to exploit)
- Privileges Required: Low (just needs an authenticated user)
- User Interaction: None required
- Scope: Changed (can affect resources beyond the vulnerable component)
- Impact: High on confidentiality, integrity, and availability
The "Changed" scope is particularly concerning. It means an attacker who compromises n8n can potentially pivot to other systems the n8n process has access to, including databases, APIs, and internal networks.
Who's affected?
You're affected if you're running:
- n8n versions before 1.123.17
- n8n versions 2.0.0 through 2.4.4
- n8n version 2.5.0
This includes:
- Self-hosted n8n instances
- Docker deployments
- npm installations
- Any custom deployments
n8n Cloud users: Check with n8n directly, but cloud instances are typically patched automatically.
How to check your version
Docker
docker exec -it <container_name> n8n --version
npm
n8n --version
From the UI
Go to Settings → About in your n8n instance.
How to fix it
Update via Docker
# Pull the latest image
docker pull n8nio/n8n:latest
# Or pull a specific patched version
docker pull n8nio/n8n:1.123.17
# Restart your container
docker-compose down && docker-compose up -d
Update via npm
npm update n8n -g
# Or install a specific version
npm install n8n@1.123.17 -g
If you can't update immediately
If you absolutely cannot update right now:
- Restrict access to your n8n instance to only trusted users
- Review user accounts and remove any unnecessary access
- Monitor logs for suspicious activity
- Plan your update for the earliest possible time
These mitigations reduce risk but don't eliminate it. An update is the only real fix.
What this means for n8n users
This vulnerability underscores the importance of keeping your automation infrastructure up to date. n8n is a powerful tool, but with that power comes responsibility for security hygiene.
As an n8n Certified Expert Partner, we recommend:
- Subscribe to security advisories from n8n and GitHub
- Implement a regular update schedule for your automation tools
- Use least-privilege access for n8n accounts
- Monitor your n8n logs for unusual activity
- Consider network segmentation to limit blast radius if compromised
Timeline
- Disclosure date: January 2026
- Patched versions released: 1.123.17, 2.4.5, 2.5.1
- This advisory published: January 30, 2026
Resources
Need help securing your n8n deployment? We're an n8n Certified Expert Partner with 3+ years of experience building production-grade workflows. Book a call to discuss your setup.
Stop guessing. Find your first workflow.
The SMB AI Readiness Assessment - a 20-minute worksheet that finds the one workflow worth fixing first, and the one gap to close before you spend.
Related Posts
AI for property management: what it handles, what it breaks, and what it costs
Property management is mostly relay work, and that is exactly the shape automation is good at. What it handles reliably, where it creates legal exposure, and what it costs.
AI receptionist for small business: what it handles, what it ruins, and what it costs
An AI receptionist answers the calls you are currently missing. The decision is not whether it works, it is which calls it is allowed to take, and what a missed call is worth to you.
AI agents for small business (2026): what they actually do, what they cost, and when not to buy one
AI agents complete multi-step jobs across your tools without someone driving them. Here is what the categories are, what they cost, and the three questions that tell you whether to buy one or leave the process alone.