Is there a patch available for CVE-2026-54311?

Yes, a patch is available for CVE-2026-54311. Update the affected software to the latest version immediately.

n8n CVE-2026-54311

Q: What is the CVSS score of CVE-2026-54311?

CVE-2026-54311 has a CVSS 4.0 base score of 6.0 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-38471 MEDIUM

Exposure of Data Element to Wrong Session (CWE-488)

2026-06-16 https://github.com/n8n-io/n8n

GHSA-9c38-2mcm-q7f7

Information Disclosure

6.0

CVSS 4.0 · Vendor: https://github.com/n8n-io/n8n

Severity by source

Vendor (https://github.com/n8n-io/n8n) PRIMARY

6.0 MEDIUM

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.3 MEDIUM

Network-accessible but AC:H for multi-user and Merge-SQL-mode prerequisites; PR:L for authenticated low-privileged workflow creator; S:C and C:H for cross-user data interception; no integrity or availability impact confirmed.

3.1 AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (https://github.com/n8n-io/n8n).

CVSS VectorVendor: https://github.com/n8n-io/n8n

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

CVSS changed

Jun 23, 2026 - 17:07 NVD

6.3 (MEDIUM) 6.0 (MEDIUM)

Source Code Evidence Fetched

Jun 16, 2026 - 19:55 vuln.today

Analysis Generated

Jun 16, 2026 - 19:55 vuln.today

DescriptionCVE.org

Impact

An authenticated user with permission to create or modify workflows could pollute the sandbox used by the Merge node's SQL Query mode. Because the sandbox context was cached and reused across all workflow executions on the instance, prototype mutations introduced by one user's workflow persist into subsequent Merge SQL executions belonging to other users or projects. This allowed a low-privileged attacker to intercept workflow data processed by other users on the same instance.

This issue only affects multi-user n8n instances where more than one user has permission to create and execute workflows containing the Merge node in SQL Query mode.

Patches

The issue has been fixed in n8n versions 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Limit workflow creation and editing permissions to fully trusted users only.
Disable the Merge node by adding n8n-nodes-base.merge to the NODES_EXCLUDE environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

AnalysisAI

Prototype pollution in n8n's Merge node SQL Query mode enables cross-user workflow data interception on multi-user instances. A low-privileged authenticated user can inject JavaScript prototype mutations into a shared, cached sandbox context; because that sandbox is reused across all workflow executions on the instance, the mutations persist into subsequent Merge SQL executions belonging to other users or projects, exposing their workflow data. Vendor-released patches are available in versions 2.25.7 and 2.26.2; no public exploit code or CISA KEV listing has been identified at time of analysis.

Technical ContextAI

n8n is an open-source workflow automation platform distributed as the npm package pkg:npm/n8n. The Merge node offers a SQL Query mode that evaluates JavaScript-based SQL expressions inside a sandbox. The root cause is CWE-488 (Exposure of Data Element to Wrong Session): the sandbox context object is cached and reused across all workflow executions on the instance rather than being instantiated per-execution or per-user session. JavaScript prototype pollution - a technique where an attacker mutates base prototypes such as Object.prototype - survives within this shared, mutable context. Any subsequent code running in the same sandbox inherits the polluted prototype chain, allowing the attacker's injected behavior to intercept or manipulate data structures belonging to other users' workflow executions. Affected CPEs are pkg:npm/n8n versions below 2.25.7 and versions 2.26.0 through below 2.26.2.

RemediationAI

The primary remediation is to upgrade n8n to version 2.25.7 or 2.26.2 (or any later release), as confirmed by the vendor in GHSA-9c38-2mcm-q7f7 (https://github.com/n8n-io/n8n/security/advisories/GHSA-9c38-2mcm-q7f7). If immediate upgrade is not feasible, two temporary mitigations are available. First, restrict workflow creation and editing permissions to fully trusted users only, which limits the set of principals who can introduce prototype mutations - trade-off: reduces collaborative use of the platform and does not protect against an already-compromised trusted account. Second, disable the Merge node instance-wide by adding n8n-nodes-base.merge to the NODES_EXCLUDE environment variable - trade-off: removes Merge node functionality from all workflows on the instance. The vendor explicitly states that neither workaround fully remediates the risk and that they should be used only as short-term measures pending upgrade.