CVE-2026-1470
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedn8n 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencen8n workflow automation platform contains a critical RCE vulnerability in its expression evaluation system. Authenticated users can supply malicious expressions during workflow configuration that execute in an insufficiently isolated context from the underlying Node.js runtime, allowing arbitrary code execution with n8n process privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.123.17>= 2.0.0, < 2.4.5= 2.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine n8n version via CLIRun `n8n --version` if n8n is installed as a CLI tool, or check the package.json file in the installation directory for the version fieldAffected if The installed version is below 1.123.17, between 2.0.0 and 2.4.4 inclusive, or exactly 2.5.0
-
Determine n8n version via APIIf the instance is accessible, make an authenticated GET request to the `/rest/settings` endpoint and inspect the `version` field in the responseAffected if The reported version falls within any of the affected ranges: < 1.123.17, >= 2.0.0 and < 2.4.5, or exactly 2.5.0
-
Check if user authentication is enabledInspect the n8n configuration file (typically `~/.n8n/config` or environment variables N8N_AUTH_EXCLUDE_ENDPOINTS, N8N_JWT_AUTH_ENABLED) or check the n8n UI login page availabilityAffected if The instance allows unauthenticated access or uses weak/default credentials, making the RCE trivially exploitable by any attacker
-
Verify workflow expression usageReview existing workflows in the n8n UI under the Workflows section, or query the `/rest/workflows` API endpoint, looking for any workflows that use Expression nodes or {{ }} syntax in node parametersAffected if Any workflow exists that evaluates user-supplied expressions, as this is the attack vector for CVE-2026-1470
A user is affected if their n8n version is within the ranges < 1.123.17, >= 2.0.0 and < 2.4.5, or exactly 2.5.0, AND authenticated users or attackers can create or modify workflows with expressions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.123.172.4.5
Apply vendor-supplied patches when available; until then, restrict authenticated user permissions to untrusted accounts, implement network segmentation, and monitor for unauthorized workflow modifications or suspicious process behavior.
n8n 1.123.17+ (for 1.x) or n8n 2.4.5+ (for 2.x, or 2.5.1+ if on 2.5.0)
- 1. Back up your current n8n instance, including workflows, credentials, and configuration files.
- 2. Identify your current n8n version by checking the n8n UI (Settings > About) or running `n8n --version`.
- 3. If running 1.x version (< 1.123.17): Upgrade to n8n version 1.123.17 or later.
- 4. If running 2.x version (>= 2.0.0 and < 2.4.5): Upgrade to n8n version 2.4.5 or later.
- 5. If running version 2.5.0: Upgrade to n8n version 2.5.1 or later.
- 6. For Docker users: Pull the new image (e.g., `docker pull n8nio/n8n:1.123.17` or `n8nio/n8n:2.4.5`) and recreate the container with your existing volume mounts.
- 7. For npm installations: Run `npm install -g n8n@latest` or specify the version (e.g., `npm install -g [email protected]`).
- 8. After upgrade, verify the n8n service is running and accessible.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,016.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data