CVE
n8n remote code execution via expression sandbox escape
- Exploited
- No known exploitation
- Fix
- Fixed in 1.123.89, 2.46.1, 2.45.5, 3.0.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. n8n versions before 1.123.89 (also 2.x before 2.46.1 or 2.45.5, and 3.x before 3.0.1, per the affected version ranges) Attacker must have permission to create or modify workflows
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
n8n before 1.123.89 contains an insufficient isolation vulnerability in workflow expression evaluation that allows authenticated users to escape the sandbox. Attackers with permission to create or modify workflows can craft expressions referencing unexpected JavaScript properties to execute arbitrary code on the n8n host.
Who should check
Teams running self-hosted n8n before 1.123.89, 2.45.5, 2.46.1 or 3.0.1, especially where users can create or modify workflows. Check n8n instances used by workflow authors.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.7/10CVSS 7.7
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
n8n versions before 1.123.89 (also 2.x before 2.46.1 or 2.45.5, and 3.x before 3.0.1, per the affected version ranges) Attacker must have permission to create or modify workflowsUpgrade to a fixed version: 1.123.89, 2.46.1, 2.45.5, 3.0.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126391 (n8n before 1.123.89 RCE via Workflow Expression Evaluation Sandbox Escape), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126391 (entry last updated 2026-11-13):
Affected:
- n8n-io n8n: fixed in 1.123.89
- n8n-io n8n: from 2.46.0, fixed in 2.46.1
- n8n-io n8n: from 2.0.0, fixed in 2.45.5
- n8n-io n8n: from 3.0.0, fixed in 3.0.1
Fixed versions: 1.123.89, 2.46.1, 2.45.5, 3.0.1.
Conditions (all must be true for the bug to be hit):
- n8n versions before 1.123.89 (also 2.x before 2.46.1 or 2.45.5, and 3.x before 3.0.1, per the affected version ranges) (source: https://www.vulncheck.com/advisories/n8n-before-1.123.89-rce-via-workflow-expression-evaluation-sandbox-escape)
- Attacker must have permission to create or modify workflows (source: https://www.vulncheck.com/advisories/n8n-before-1.123.89-rce-via-workflow-expression-evaluation-sandbox-escape)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126391 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126391 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/n8n-io/n8n/security/advisories/GHSA-gx3v-3x3v-f8r5
- https://www.vulncheck.com/advisories/n8n-before-1.123.89-rce-via-workflow-expression-evaluation-sandbox-escape
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126391
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126391"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- n8n-io n8n
fixed in 1.123.89
- n8n-io n8n
From 2.46.0 · fixed in 2.46.1
- n8n-io n8n
From 2.0.0 · fixed in 2.45.5
- n8n-io n8n
From 3.0.0 · fixed in 3.0.1
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126391
Is CVE-2026-126391 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Workflow expressions in n8n are meant to run inside an isolated sandbox. A user who can create or modify workflows can craft expressions that reference unexpected JavaScript properties and escape that isolation, running arbitrary code on the n8n host.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126391?
n8n: before 1.123.89. n8n: from 2.46.0 before 2.46.1. n8n: from 2.0.0 before 2.45.5. n8n: from 3.0.0 before 3.0.1.Source: cve.now feed data
Am I affected, and how do I check?
The affected ranges are n8n before 1.123.89, 2.x before 2.46.1 or 2.45.5, and 3.x before 3.0.1. The version can be checked by running the n8n version command on the host or by viewing the version in the n8n interface. Exposure also depends on whether users have permission to create or modify workflows.Source: vulncheck.com, github.com
How do I fix CVE-2026-126391?
Upgrade to 1.123.89 or later on the 1.x line, 2.46.1 or 2.45.5 on the 2.x line, or 3.0.1 on the 3.x line. The facts do not list a separate workaround.Source: vulncheck.com, github.com