CVE-2026-54311
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 is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, 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. This vulnerability is fixed in 2.25.7 and 2.26.2.
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 · high confidenceIn n8n workflow automation platform prior to versions 2.25.7 and 2.26.2, the sandbox context used by the Merge node's SQL Query mode is cached and reused across all workflow executions on the instance. An authenticated user with workflow creation/modification permissions can perform JavaScript prototype pollution by injecting properties into Object.prototype through the sandbox. Because the sandbox context persists across executions, these mutations affect subsequent Merge SQL executions belonging to other users or projects, allowing a low-privileged attacker to intercept or manipulate workflow data processed by other users.
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< 2.25.7>= 2.26.0, < 2.26.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
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.
-
Identify installed n8n versionRun `n8n --version` from the command line, check the About page in the n8n UI (Settings > About), or inspect the package.json file in the n8n installation directoryAffected if The installed version is less than 2.25.7, or greater than or equal to 2.26.0 but less than 2.26.2
-
Verify if Merge node SQL Query mode is in useReview all workflows in the instance and identify any that contain a Merge node configured with the SQL Query mode. In n8n, inspect workflow JSON definitions or use the UI to check each workflow's node configurationAffected if Any workflow on the instance uses a Merge node with the SQL Query mode enabled, regardless of whether it contains malicious code
-
Confirm multi-user mode is enabledCheck n8n settings or environment configuration for user authentication settings. Look for `N8N_AUTH_EXCLUDE_ENDPOINTS` or similar multi-user configuration flags, or verify that user management is active in the instanceAffected if The n8n instance has multiple users or projects configured, as the vulnerability allows cross-user prototype pollution affecting other users' workflow data
-
Detect prototype pollution in Object.prototypeExecute a JavaScript check in a workflow or script to inspect Object.prototype for unexpected properties. Run: `console.log(Object.keys(Object.prototype))` in a workflow node to list any properties that should not exist on the base ObjectAffected if Object.prototype contains unexpected or suspicious properties that were not intentionally added, indicating successful prototype pollution
You are affected if your n8n version falls within the vulnerable range AND any workflow uses the Merge node in SQL Query mode on a multi-user instance, with prototype pollution detectable in Object.prototype.
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 · scoped2.25.72.26.2
Upgrade n8n to version 2.25.7 or 2.26.2. On multi-user instances, restrict permissions to create workflows with the Merge node in SQL Query mode until the upgrade is applied.
Upgrade to n8n 2.25.7 or 2.26.2 (or later respective to your branch)
- 1. Identify the current n8n version by checking the instance or running `n8n --version`
- 2. If the current version is < 2.25.7 on the 2.25.x branch, upgrade to version 2.25.7 or later (e.g., `npm install [email protected]` or use your deployment method)
- 3. If the current version is >= 2.26.0 and < 2.26.2, upgrade to version 2.26.2 or later
- 4. After upgrading, verify the new version is running: `n8n --version`
- 5. Test that the Merge node in SQL Query mode functions correctly after the upgrade
- 6. For multi-user instances, confirm that workflow executions are properly isolated between users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54311 — 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-54311 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